Unable to locate sign at XX, XX, XX

[su44us]

Hello.. I recently upgraded to MC 172 (from 164) and subsequently forge-1.7.2-10.12.0.1024 (I have also tried 1029 client, although I did not update the server).  After upgrading to 172, everything was working fine. However when I add Minecraft Forge I get text messages immediately upon entering the server (I am running a Linux server) stating "Unable to locate sign at XX, XX, XX".  The sign locations seem random, and there are usually only 2 - 3 messages upon logging in.  If I move to a previously unloaded chunk I will possibly get more messages.

 

I have scoured the web and these forums for such a problem and have found 1 posting on these forums which was resolved several releases ago.

 

I have reinstalled both the server and client side applications with no change in status.  I have installed a fresh client on a computer which has not previously run minecraft with the same outcome.  I have searched both server and client logs and only find the messages in the MC latest log for the client.  I have removed forge and verified that the messages do not occur in my vanilla MC, then re-added forge to once again receive the messages.

 

Thank you for your time.

 

Here is the FML latest log - http://pastebin.com/e4gBzKkk  Let me know if you need anything else.

[LexManos]

Your server is telling your client that there is a sign at that location, without there actually being a sign there.

Either some mod you have installed is derping up, or something happened to signs. I just verified locally that Forge doesn't screw up signs.

[su44us]

Perhaps I should have mentioned this, but I have teleported to the coordinates, and there are indeed signs at every location I have teleported to.  This is occurring with no mods whatsoever besides forge, and definitely does not happen without forge.  Also, there is a post on here from January of last year with someone reporting a similar problem (although thier also consisted of missing pieces of their world which mine does not), but that issue was addressed in an earlier release.

 

I am 100% sure this has something to do with forge as I have tested extensively and it only happens when I enable forge, and with no other mods.

 

This is a fairly old world, and has MANY signs (in caverns and such).. Perhaps it has something to do with the number of signs?

[LexManos]

Number of signs would be no issue.

Give me your world so I can try to reproduce.

The issue is your client thinks there is no sign where the thing tells it there is supposed to be a sign.

Also, side note, your log doesn't line up with what you're saying {namely it doesn't have the error}

Nothing we can do to speculate as we can not reproduce it on our end, so either give us your world and hope we can reproduce, or try and figure it out yourself.

[su44us]

Thank you for the offer to try to reproduce the error with my world on your end.  I realized that I hadn't tried running the world in SP mode. So hoping to save you the trouble, I tried that this morning on my computer at work.  This PC had not run MC before, and once again I used no mods other than Forge.  Same thing, without forge I get no missing sign messages.  When I enable forge however, I get the messages. 

 

I also tried teleporting to the sign locations, removing and re-adding them to see if that would keep those signs from being reported as missing but I still get messages for the ones I switched out..

 

Here is the link to my world.  I wish you luck, and once again, thanks for taking the time.

 

https://drive.google.com/file/d/0BxTZeFsVvP8VVGo0VlIyQzkyX0E/edit?usp=sharing

[LexManos]

Alright, now that I got your world I was able to reproduce.

This was happening for signs that were exactly on the 0 index of a chunk RIGHT outside your loaded chunk range.

It is actually a vanilla Minecraft issue, vanilla just likes to eat the information, and leak a bunch of stuff instead of complaining like it should.

Fixed here Note the change from '16' to '15' {Got to love programming u.u}

[su44us]

That was fast, thanks!

 

Now a couple questions (or 3)

 

So this is basically a minecraft bug that doesn't get reported normally but does with Forge?

I assume this has no long term detrimental effect on my world?

When you say, "fixed" do you mean you have fixed the error through the Forge mod (in essence cleaning up a vanilla MC bug?), so it will be "fixed" in a future Forge release?

[LexManos]

Yes, its a normal minecraft bug that isn't reported because in vanilla it silently leaks tons of chunks in memory. With possible detrimental effects to the world/run.

With the fixes we put in Forge, there should be no detrimental effects anywhere. The fixes make it so that there are FAR less abandoned chunks out there that the just sit in memory slowing your game down.

When I said fixed, I also linked the commit that I pushed that fixed it. Every time we push to github it builds another version of Forge, which you can download from our downloads page. So, the fix is available now. Go get it. And yes, basically we fixed a vanilla bug, we do that quite often in Forge.

[su44us]

 

Awesomeness! I will light an incense in the altar tonight for the code god.

[su44us]

Just to confirm, it worked.