Cool VL Viewer forum

Sometimes the viewer crashes to desktop for no reason I can identify. Sometimes it will crash three times in a row, other times it will not crash at all for days. However, when it does crash and I reopen it and reconnect, almost always it will be unable to download the world and/or interact with it; i will be a cloud, the sim won't rez, it will see my legacy name but not my display name, typing in the chat and moving about won't do anything; it's like the viewer hasn't truly connected to the server. If I relog, then everything will be fine. I cannot say when it started, if it is connected to a kernel/mesa update. But I am posting yesterday's log, before and after the crash, in the hope that it'll help.

Note: After the crash, a stack_trace.log file was created, but it's empty.

The reason for the crash seems to be an issue with the available memory (VRAM, or maybe RAM too) and your graphics driver:
However, since you did not provide stack_trace.log, I cannot diagnose the root cause (even if it is likely an "out of memory" bug: reduce your VRAM usage via the viewer Graphics settings).

As for the problem seen when reconnecting immediately after a crash (or a failed TP causing a disconnection, or your network going down and causing you to get disconnected, etc), this is a known issue with the (relatively: a few months old) recent changes done to SL's "presence server": when the viewer cannot disconnect properly (which is the case when it crashes), the presence server still thinks you are connected, and the simulator gets confused, and does not send its data to the new connection you created by relogging.
To avoid this issue, simply wait 3 minutes before reconnecting, or reconnect once, disconnect immediately, and reconnect a second time.
This is not something I can "fix" from the viewer side...

As I said above, stack_trace.log was created, but when I opened it it was empty. I shall reduce my VRAM usage and see how that fares. It happens on laggy places, but also in non-laggy, however. It is weird. Thank you for the explanation, I shall follow it and see.