Movement/IK starts lagging after staying ~35 hours in the same instance
Fusl
As title says, after staying for more than 35 hours in the same instance without reconnect or rejoin, the movement/IK of such players starts lagging and jittering, the update interval increases and the user shows as delay > 1 seconds in the network debug menu (see attached screenshot).
Log In
E
Erimel
Reproduced on https://www.youtube.com/live/F8hkvrX2j0Q?feature=share
thebutlah
Erimel: For added context, this was on a charity livestream, and as the livestream went on, the IK became impossibly jarring to watch.
Kanĩ
Cant Believe this happen to me but every 10,15 minutes on a instance
two videos about this problem
OP_Buster
Just asking, who TF spends over 35 Hours in the Same Instance?
danly
...
Could you tell me the memory usage of VRChat.exe at that point?
Fusl
danly: 1,422.7 MB according to task manager
T
TCL
Fusl: Can you also check the "Commit Size"? You can see it in Windows' Resource Monitor. You can open Resource Monitor from the Task Manager's Performance tab. In Resource Monitor open the Memory tab and find VRChat.exe in the processes list. There will be columns for Commit, Working Set, Shareable, and Private memory usage.
Fusl
TCL: 3,288,040 Commit, 2,062,624 Working Set, 81,088 Shareable and 1,581,544 Private
T
TCL
Fusl: How many hours has the client been running?
Fusl
TCL: "Started: 2019-12-14T23:17:34Z" so around 3 days, and that particular client is in the same instance for around 63 hours already.
`Squishy
This seems like a bug that surely has the least reasons to spend time fixing, but I suppose there's no harm reporting it. Just out of curiosity, what would anyone actually want to do this for? Some kind of social experiment, or self destructive streaming challenge?
Deskclaw
Interesting that you could stay in a single instance for that long, but that's besides the point. +1