D2DBS: pvpgn::packet_get_size: packet has bad size XXXX

[fenghou1st]

I got this error approximately every 10 minutes.
Code branch: master.

Jul 10 08:21:47 [info ] pvpgn::d2dbs::dbs_packet_savedata_charsave: saved charsave bot_vii(*bot07) for gs 10.0.0.2(1)
Jul 10 08:21:47 [info ] pvpgn::d2dbs::dbs_packet_updateladder: update ladder for Bot_VII@Fenghou's Private Realm for gs 10.0.0.2(1)
Jul 10 08:21:47 [info ] pvpgn::d2dbs::dbs_packet_savedata_charinfo: saved charinfo bot_vii(*bot07) for gs 10.0.0.2(1)
Jul 10 08:21:47 [info ] pvpgn::d2dbs::dbs_packet_charlock: unlock character Bot_VII(*Bot07)@Fenghou's Private Realm for gs 10.0.0.2(1)
Jul 10 08:22:04 [info ] pvpgn::d2dbs::dbs_packet_savedata_charsave: saved charsave bot_viii(*bot08) for gs 10.0.0.2(1)
Jul 10 08:22:04 [info ] pvpgn::d2dbs::dbs_packet_updateladder: update ladder for Bot_VIII@Fenghou's Private Realm for gs 10.0.0.2(1)
Jul 10 08:22:04 [info ] pvpgn::d2dbs::dbs_packet_savedata_charinfo: saved charinfo bot_viii(*bot08) for gs 10.0.0.2(1)
Jul 10 08:22:04 [info ] pvpgn::d2dbs::dbs_packet_charlock: unlock character Bot_VIII(*Bot08)@Fenghou's Private Realm for gs 10.0.0.2(1)
Jul 10 08:22:28 [error] pvpgn::packet_get_size: packet has bad size 3134
Jul 10 08:22:28 [error] pvpgn::packet_get_size: packet has bad size 3134
Jul 10 08:22:28 [warn ] pvpgn::net_recv_packet: [1148] corrupted packet received (total_size=0 currsize=8) (closing connection)
Jul 10 08:22:28 [debug] pvpgn::d2dbs::sd_tcpinput: [1148] read returned -1 (closing connection)
Jul 10 08:22:28 [info ] pvpgn::d2dbs::conn_destroy: [1148] unlock all characters on gs 10.0.0.2(1)
Jul 10 08:22:28 [info ] pvpgn::d2dbs::conn_destroy: [1148] closed d2gs connection
Jul 10 08:22:33 [info ] pvpgn::d2dbs::sd_accept: [1148] accepted connection from 10.0.0.2:54541 on 0.0.0.0:6114
Jul 10 08:22:33 [info ] pvpgn::d2dbs::sd_accept: [1148] set KEEPALIVE option
Jul 10 08:22:33 [info ] pvpgn::d2dbs::conn_create: [1148] created connection serverip=10.0.0.2 serverid=1
Jul 10 08:22:33 [debug] pvpgn::d2dbs::sd_accept: [1148] client connected to a d2gs listening address
Jul 10 08:22:33 [info ] pvpgn::d2dbs::handle_init_packet: [1148] client initiated d2gs connection
Jul 10 08:22:33 [info ] pvpgn::d2dbs::dbs_verify_ipaddr: [1148] ip address 10.0.0.2 is valid
Jul 10 08:23:03 [info ] pvpgn::d2dbs::dbs_packet_getdata: lock char Bot_VIII(*Bot08)@Fenghou's Private Realm for gs 10.0.0.2(1)
Jul 10 08:23:03 [info ] pvpgn::d2dbs::dbs_packet_getdata_charsave: loaded charsave bot_viii(*bot08) for gs 10.0.0.2(1)
Jul 10 08:23:03 [info ] pvpgn::d2dbs::dbs_packet_getdata_charinfo: loaded charinfo bot_viii(*bot08) for gs 10.0.0.2(1)

[RElesgoe]

Can you double check which branch your pvpgn was compiled from?

[fenghou1st]

I redownloaded and recompiled the project and replaced the release files, according to issues 458, then that error never appeared again.
Since I have replaced the files, I can't be 100% sure that it was the master branch. But I have been using the master branch, unless I made a mistake.

[RElesgoe]

That change from my comment in #458 is intended for the develop branch. If you’re experiencing this error with code from the master branch, then this needs further investigation.

[fenghou1st]

Yes, I know. Sorry I can't give more useful information.

[Marfjeh]

This issue started happening on my machine as well. after doing Act 2 nightmare mode after completing Tal Rasha's Chamber then it will kick everyone in the game. even playing alone this will happen for that person only. and will get rolled back even though my character did not get rolled back and i was in the same game.

But weirdly enough the person already completed nightmare mode on other characters so far i'm aware. this leads me to suspect that his character is maybe currupted?

Our clients are Diablo 2 1.13c with the glide wrapper, Cpufix, and the widescreen mod.
only difference is that my friend is playing on Windows 11. and i'm playing on Linux under wine.

I think that i'm using the master branch. however i did use pvpgn-magic-builder and have now applied the patch as you pointed out in #458 to increase the max packet size and recompiled everything. I'll report back if it happens again.