I don't know if this will help anyone, but i kind of randomly found out that if you hit the refresh visible button, and keep moving your mouse around until it is COMPLETELY finished reloading all the servers, it tends not to crash. So I don't know if it is a fluke, or my imagination, but try it.

shadowraith wrote:I don't know if this will help anyone, but i kind of randomly found out that if you hit the refresh visible button, and keep moving your mouse around until it is COMPLETELY finished reloading all the servers, it tends not to crash. So I don't know if it is a fluke, or my imagination, but try it.

Yea this kills me with 1.40, it must happen to me like 10-15 times a day.

shadowraith wrote:I don't know if this will help anyone, but i kind of randomly found out that if you hit the refresh visible button, and keep moving your mouse around until it is COMPLETELY finished reloading all the servers, it tends not to crash. So I don't know if it is a fluke, or my imagination, but try it.

Yea this kills me with 1.40, it must happen to me like 10-15 times a day.

Why do you refresh so many times a day?

I start tribes, hit quick start button to skip the player profile menu and go right to server list.. It auto-refreshes once... I check the info of a few populated servers to get the active player count and see who is actually playing before I pick a server, then a pick a server and play till the server crashes, until I get bored/frustrated, or until I have to go do something else. Then I close tribes and do something else, or restart tribes and look for another server.

I don't think I ever disconnect from a server and refresh the server list... That's just asking for trouble.

I've traced the crash to the rendering code. One of these days I will produce a fix. Maybe. Perchance, the same buffer overflow is causing both. I don't think that's the case though because they're using different controls.

A lot of factors, but the typical buffer overflow is a relatively easy fix. The server info fix was probably 10-15 minutes. The server list fix will take longer because it's not a simple buffer overflow. I might have time to fix it today, still.

By removing the player-stats update from the game info packet, I was able to remove the crash. However, I still haven't tracked the actual 'condition' that's causing the crash. This is a weird one ... and it's alluding me. I could just kill off the player-stats update, but you guys don't want that ... at least I don't think? lol.