New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verbose logging bloated regression #2636
Comments
Additional information: when I'm adding to |
Datas.size is set in packet constructor , this reserve packet size directly instead of reallocate memory in putRawString. I will look at a modification on this handler tomorrow, this copy isn't needed, we should write datas to packet directly |
I don't understand: Where is a copy? |
I think the problem is that The client, after processing the good first half of the packet, runs into the spurious zeros and interprets each 4 bytes as a message for object 0 of zero length. For each spurious message, the client then complains that it can't find object 0. |
When you are starting minetest in singleplayer (connecting to remote servers triggers this too) and are running with the
--verbose
flag, you get many many messages of the kindINFO[main]: ClientEnvironment::processActiveObjectMessage(): got message for id=0, which doesn't exist
.I have found out that commit 8804c47 has caused this regression, to be more precise the change that replaced
0
withdatas.size()
inNetworkPacket pkt(TOCLIENT_ACTIVE_OBJECT_MESSAGES, 0, peer_id);
. If you change it back to 0, the messages disappear. This isn't of course a proper fix of the root cause, which either lies in networkpacket, or some other lower layer networking code. Therefore medium priority.@nerzhul can you have a look at this?
The text was updated successfully, but these errors were encountered: