Cool VL Viewer forum

ever since I updated to coolrelease 1.23.4.0.12 I keep freezing up, and in top i see secondlife-bin eating all my ram.
I don't think it was that bad on the original viewer...

The only real change, code-wise, between release 11 and 12 is the new radar floater. If you think it might be the cause of your problem, just don't open it during the whole session and see if it makes any difference, but I doubt so (no memory leak in the code, as far as I can see).

I don't experience either such troubles myself, so I can't reproduce any such issue.

Question: did you change anything to your system, beside the update from release 11 to 12 ?... A graphic driver change could explain those symptoms, for example.

nope, graphics driver hasn't been updated for quite some time... but KDE4 itself gets updates all the time...


anyways, what i see in htop is that the sl binary starts to eat up ram like crazy, to a point where i can hardly move at all. i will try that "don't use the radar" and see if that changes anything.

I logged in, completely disabled the radar, and watched the memory usage.
Pretty constant at 1.4 GB ram allocated. Didnt actually go anywhere, just standing around outside.

Then I switched on the radar (alerts on "enters sim" and "enters chat range" to local chat even with radar floater closed), stayed at the same spot, and kept watching the memory usage...

in maybe 10 minutes the allocated memory went up to 2GB, and there werent any actual people around triggering the radar alerts...


Building a CV12 with the two patches for the radar removed for local testing now.

I'll keep you updated.

hm.

CoolViewer R12, with the radar patches NOT part of the build, and memory usage never went over 1.9GB virtual memory, and went down to 1.6GB quite often... whereas your build WITH the two radar patches went over 2.1GB and didn't go back down after a TP to a quieter area...


seems there really might be a leak in the radar code.
Or maybe the radar just simply caches too much data internally.

I never get over 1Gb or so here... But yes, the radar caches data for too long a time (1 hour !) for each new avatar which gets detected in surrounding sims.

Note also, that increasing the draw distance to 512m will make more avatars detected, but also more of them will be within draw distance and thus "focusable": focusing on all avatars in draw distance with the Next and Previous radar buttons can in turn dramatically increase the memory usage of the viewer, not because of the radar itself, but because by focusing the camera into other sims, you trigger the caching of a ton more textures and objects in the virtual file system (VFS) that the viewer uses (think of it as a sort of a dynamic RAM disk)...

I'm currently putting the final touch to version 2 of the patch, with this issue corrected and more refinements added (Focus/Next/Previous buttons automatically disabled for avatars beyond draw distance, distance number color black for avatars beyond draw distance, manual announce button for HUDs in the Options tab, etc...).

The next release should come in the next few days, depending on how goes the RestrainedLife v1.21 patch (Marine's v1.21.1 is still buggy and I need to see if I can fix an annoying bug in it).

All that i can say so far is that a coolrelease 12 compiled without the radar seems to use about 30% less memory...

Haven't done much testing though, and conveniently enough i'm about to run off to a weekend vacation in prague.