|
|
|
[
Permlink
| « Hide
]
Kevin Susenko added a comment - 15/Nov/07 09:12 AM
Removed FirstLook: WindLight from the affected versions list since it does not only affect the windlight viewer.
After a while, I must say that the Windlight client, especially the newer version, does seem to be a bit more stable. It hasn't crashed Windows yet, only itself.
The low FPS problem is still the same, even with lowest graphic settings I still get 0.5-3 FPS in some places, while I get 40-60 FPS a few steps later. The new lag meter says that it's due to "images loading" and "ping time over 600 ms"; when I walk away a bit, all is green again. Some more insights on low FPS... it always happens when there are more avatars present and displayed on screen. More avatars means more lag - I've got 3 FPS with 10 avatars, and 6 FPS with 5 avatars and so on. Avatar impostors don't really help. I'm attaching the screenshot which shows what happens with 6 avatars... 10 FPS compared to usual 60 FPS when noone is around.
Also, the same seems to be true when a lot of objects are around. I always see low FPS when walking around NCI at Fisherman's Cove, for example. The problem is the same for the last 6 months I've been using, and through all clients - both regular and Windlight. Hello,
I have been working on troubleshooting SL on my Vista installation for six weeks by now. I am using a X38 chipset and E6600 CPU, 4 GB RAM, 8800GTS-320 card, and a parallel installation of Windows Server 2003 and Vista X64 and x86. ANY kind of SL client that I have tried (1.18.5.3, any flavor of 1.19, Windlight or not regardless) would increase it's footprint until it starts popping up out of heap memory errors around 1.3 - 1.5 GB of memory usage in Vista after 2-4 hours of running. This is VISTA SPECIFIC, I want to stress that. In older Windowses the client would flush old data once you minimize the SL window and barely leave a footprint of 54 MB. This definetly HAS TO BE FIXED, people. It doesn't only lead to client crahses but also to total OS crashes. I've just wanted to add - I don't get memory errors with Vista, so Amurtigress' experience is not shared by all Vista users and perhaps not easily reproducable - and we have similar hardware.
What I've noticed recently though is more random crashes than usual after I've started using RC after Windlight client has merged with it. It seems that Windlight was a bit more stable... An addition by me. I had a friend over last sunday and I put my graphics card into his computer. Main differences are a ASUS P5B Deluxe board with 965 chipset and "only" 2 GB.
We had the exact same issues there. To me the memory error makes sense. You have to know that any Windows application can only allocate 2 GB of RAM, and is limited to 2 GB minus the amount of graphics memory that your card has. Because 3D applications written for pre-Vista OSses are obliged to keep a copy of the graphics memory in it's own adress space.This fits very well to the 1.5 GB. I am just guessing myself. I have also asked other Vista users on SL who just saw the memory consumption go up as I did, and never flushing upon minimization as it should in Win2003. Could it be that the Lindens are relying upon the user to minimize windows and thus manually flush the most part of used RAM? The used memory amount does decrease somewhat (app. 200 MB) during operation in Vista but tendentially it just goes up.
While the AMOUNT of memory consumed may change from XP to Vista (having recently switched computers and OSs), I can say that the heap memory errors AK is commenting on here also take place in XP. The viewer gobbles insane amounts of RAM with no seeming care given to garbage collection or periodic flushing of memory. I have only rarely been able to stop a session in either the RC or the present release without getting a heap error instead of a normal program exit. I believe others have posted screencaps of the pertinent error pop-ups.
Will see whether anything happens to memory on minimize as AK suggests here. Posting the smartheap error message and typical memory snaps from first load to memory locked up when SL locks up.
These were captured crashing RC 1.20.6 – time from loading to crash roughly 2 hours. Also documented as an HP Quad core-specific issue, but the same basic error has been present in XP as well for several releases now. In XP it has usually been masked by other crashes coming first. Also, I have looked at it several way and see no signs that the RC ever releases significant amounts of memory, either when SL is minimizes or under any other conditions that others have mentioned here and in related Jira issues. Same problem, Ill be in a area with more or about 8 avatars, running flawlessly at about 40-50FPS, then all the sudden a drop to 1-2-3 FPS. Its a crippling issue and hopefully gets a fix very soon.
Hi Domchi, are you still experiencing this problem using the latest version of Second Life?
Alexa, unfortunately I'm no longer running SL on Vista; I'm back on the XP, primary reason being this very issue. Maybe other commentors can offer some input?
I'm planning to go back to Vista in the future, especially if Vista issues are fixed, so maybe I'll be able to offer some feedback then. (Of course, on the exact same hardware and XP this slowdowns never happen.) I'm on Windows 7 now (on the same hardware as before on Vista when filing this issue), and I haven't seen this happen again.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Critical
Low FPS when displaying multiple avatars and Vista crashes
