ViaRewind

ViaRewind

7.4k Downloads

Protocol 1_7_6 10 to 1_8 crash because profile is null

drori200 opened this issue ยท 10 comments

commented

/viaversion dump Output

https://dump.viaversion.com/9353cd6aa02393906f7fa85850eaf24fad27943c390247414c981b09ef10db45

Console Error

https://mclo.gs/m4mEmjg

Bug Description

Trying to join from 1.19.4 to 1.7 results in the crash submitted.

My server setup is two backends under a 1.20 velocity proxy.

Backend 1 is 1.19.4 and used as a queue server to redirect to backend 2 which is 1.7.10

The error only happens once on the first try of connecting to the queue server for some people. It will kick them once and on the next try they successful manage to join. It only happens for some players and never happens for some other players connecting with a client of the same version(1.7.10).

Steps to Reproduce

  1. Use 1.7.10 client to join the 1.19.4 server
  2. Get redirected to the 1.7.10 server and get kicked because of the error

Expected Behavior

Join the 1.7.10 server fine

Additional Server Info

No response

Checklist

commented

Platform: git--Paper--%22483368e%22%20%28MC%3A%201.19.4%29
ViaVersion (4.9.0-23w43a-SNAPSHOT): Even with dev
ViaBackwards(4.9.0-23w43a-SNAPSHOT): Even with dev

commented

Platform: git--Paper--%22483368e%22%20%28MC%3A%201.19.4%29
ViaVersion (4.8.1): Even with master
ViaRewind(3.0.0): 7 commits behind master
ViaBackwards(4.8.1): 2 commits behind master

Please try the latest build(s) from https://ci.viaversion.com/. In case the issue still persists send the new dump

commented

Please update ViaRewind to latest dev version

commented

Please update ViaRewind to latest dev version

Done. New dump:
https://dump.viaversion.com/93052b48cec32dfa7c5be836ae1c287a35b193930f207d49f9ef69a2113f23af

commented

Platform: git--Paper--%22483368e%22%20%28MC%3A%201.19.4%29
ViaVersion (4.9.0-23w43a-SNAPSHOT): Even with dev
ViaBackwards(4.9.0-23w43a-SNAPSHOT): Even with dev
ViaRewind(3.0.4-SNAPSHOT): Even with dev

commented

What's the exception you are getting now?

commented

What's the exception you are getting now?

Same exception

commented

@FlorianMichael anything new regarding this?

commented

Fixed in latest dev version