|
|
|
[
Permlink
| « Hide
]
Jana Fleming added a comment - 29/Apr/07 07:54 AM
I'm having the same problem but it only started with 1.15. I'm running NVIDIA 6800 Ultra. All drivers are updated. No firewall, no antivirus running. And like the OP, everything else on my system runs perfectly fine, as was SL until the latest upgrade
I also have the same problem of SL crashing my entire system. All service packs installed on a Windows XP 2005 Media Center laptop, with a NVIDIA GeForce 7800GTX. After logging on, I have anywhere between 5 - 10 minutes before it freezes my whole system, requiring a physical reset of the machine. As with Jana, this has only happened on the latest SL update.
Please fix this immediately, this is a very critical problem! Even though this is not a duplicate issue, the crash itself may be related – linked.
I had the same problem and like you say I was also given Version1.13.2 and you are right it fixed the problem but this update is worse than the last one for me what mine would do is it crashes the whole Computer and I have to restart the system. I run a Dell XPS Laptop running on Windows XP 2005 Media as well and Like you mine also crashes 5-10 min after start-up Even on the beta grid but it isnt as bad on that grid Yes Please for god sakes fix this problem I called the help line for Linden Labs never got through
Well it is good to see I am not the only one. Like the rest I too was given 1.13.2 to cure the 1.14.1 update. And it worked well but 1.15 update is a royal pain it is worse I also run Windows XP Media 2005. The beta grid does seem to work better when you have the version with voice but crashes the system as soon as you enter a high prim sim. On the main grid I crash almost as soon as I log in with in minutes. Please fix this problem I dont care if it means using 1.13 again as long as it works.
My computer also freezes after 5-10 min while playing the latest update 1:15 but was working fine with 1.13.2 .hope they will run 1.13.2 parallely.
I have the same problems listed above after installing 1.15 I am also going into safe mode on my computer, something that never happened with previous releases. Called Linden on the phone, but that was a fruitless venture. Many freinds in SL are having the same problem. Can something be done? Seems like each update the sitiuatins grow worde instead of better. Too bad we can't go back to last December. Everything worked great then.
I am having the same problem too. I had issues with 1.14 version crashing my system and had to revert to 1.13.2 to be able to use SL. This new version 1.15 is now causing the crashes again - and I have unchecked the VBO box in Graphics Prefs. The crash is sudden and unpredicatble always resulting in a total system restart (hard crash) which is a pain whilst DJing events as my visitors loose music for as long as it takes me to reboot my system. I have all the latest drivers, and as I said before, the previous 1.13.2 version worked without crashing like this.
Confirmation: those of you crashing are sending in crash reports, yes?
Same issue. Happened with 1.14-
I am using a graphics card that's not supported by SL. However, this has worked fine for almost a year now, which has led me to buy land and invest heavily in SL. I'm using an Acer Aspire 3610, running Windows XP Home Edition (5.1) with a Mobile intel(R) 915GM/GMS910GML Express. Has any one tried on a fresh install of XP (non-media center edition)? I guess it would help to rule out anything that might be causing it in the host environment. Could be some application that has installed some "improved" dll somewhere that doesn't behave in a way that SL code expects it to. In any case it's an SL bug, but it might help track down the issue. I'm running GF 8800 and XP64bit SP2 with not problems.
By disabling the sound, the viewer does not crash anymore.
Something maybe related to: igxprd32 Running Windows XP Media Center Edition 2002 Service Pack 2 Oops, discard my previous tip to prevent crashes, muting all sound is not a sollution........
got a blue screen (BSOD) a few minutes ago.... Tested the 1.16 viewer on the beta grid, have seen no blue screens anymore, nog systems freezes.
If it crashes, it shows a nice crash-logger window and stops silently. Can;t wait to have the new 1.16 on the main grid. System crashes with client Second Life 1.16.0 (6) May 25 2007 14:23:46
was less with 1.15 and even less with 1.14. Using Vista and although not properly supported can run sl. The NVidia 7800 pci express graphics card with driver 100.xx allows Secondlife to run but upgrade to the latest NVidia 150.xxx drivers and Second Life refuses to recognise the graphics card. I also have the same problem of SL crashing my entire system. I get the dreaded blue screen. I've sent in numerous crash reports.
I have the same problem, please help us!!!!!!!
Happens to me too. If there was a crash counter or restart counter, it'd be on 1000-5000 i'd say :O. I also have problems with video in iTunes sometimes, but only after SL freezes my PC before a few more times then BUMP!, it's frozen.
I have the same problem. My laptop is really getting hot and then boom, stop error/blue screen. It seems to be a video card issue. Updated my drivers to the latest version and it still happened.
My laptop: A Dell Latitide D520 (Oh, and I have the same exact problem in Linux as well, but in Linux it just locks up...)
can someone send the 1.13.2 download to me? i am having the same problem, running under Vista Premium.
lvmuldrow@gmail.com, systas0ul@msn.com This issue has also been happening to me for several months and I am so dispirited as it has made SL unusable.
Dell XPS Gen 2 with Nvidia Geforce6800 graphics. Within minutes of logon to SL, colours flash rainbow on textured surfaces of rendered objects and then the whole computer freezes. Please LL fix this. I rebuilt my laptop...downloaded 1.17 and guess what same issue...Can someone from LL please respond ?
I too have the same issue. Earlier today, I had it in the setup screen, before I had even logged in.
Everything is ok, and then suddenly it stops, the video stops, and all input devices are blocked. But the sound still works -there was a train passing me once. And the turkeys kept cackling. BTW, the crash report utility is also not very handy, it takes a long time to detect hardware, so if you were talking to someone, you're not very inclined to wait for that thing to do it's work. I to have had multiple issues w/ the new client. Primarily I can navigate my avatar until the mouse pointer is on the SL viewer window...then the whole thing freezes. I move my mouse off the viewer (onto the desktop) and I am unfrozen. Needless to say this presents a very tough road to hoe and I am mostly giving up on spending time in SL.
Thinkpad T60 core due I just had repeated crash issues ovr the last couple of days. Although the symptoms match what is described by the others (laptop gets very hot, then locks up - occasionally with screen "static" - and must be hard-rebooted), my own situation may be different. After several lockup crashes tonight, my laptop no longer displays anything on boot up. This bug may have caused our old laptop to kick its bucket. I'll be looking at that more in the daylight hours.
Gateway 450ROG I'm having trouble with my internet connection (on wireless at the moment), and 99% of the time SL crashes, my entire system freezes. I have to power down the compute to fix this (by holding the power button).
Windows XP Pro SP2 We need to distinguish this problem further to determine a cause(s). If SL crashes but does not freeze your entire system as originally described, please search for other related issues and create a new one if you can't find an existing one pertaining to your specific circumstances.
Please be sure to provide your system config. From the login screen, go to Preferences > click About button and copy and paste the info from the top pane here. More Residents experiencing this should comment so we have a broader range of data. This started with 1.14 (1.13. and prior did NOT have this problem). Often at log-in, and often when moving the camera some distance, or panning, and randomly at any other time, the screen turns black and the computer becomes unresponsive. Sometimes it recovers in less than a minute but with graphics artifacts that persist until the program is restarted again. But many times it does not recover, and after several minutes the only option is to lean on the power button. Thinkpad T60p, Windows XP Pro, ATI FireGL V5200 (with latest ATI driver).
Yes same freezing problem here, have submitted a system report before, updated ati drivers, unistalled and reinstalled SL properly with all the temp empting. SL runs for about 2 to 5 min then the mouse freezes, picture freezes and no sound. Half the time I can get back to windows to shut down the SL window. the other half have to turn the power off to the system. Have no problem with any other programs or apps or 3d games such as Battlefield2.
System: I've marked this as a "Meta-Issue".
What does that mean? Simply that while we likely won't be able to resolve this whole issue – as it contains a variety of reports which may or may not have the same cause – we can use it to get more details. In which case if there is a specific cause which is hopefully reproducible, then please file a separate and distinct issue, and use the "Issue Links" above to connect it to this. From the time right after you crash/freeze, please get your SecondLife.log file and attach it here. Instructions on where to find it are @: » https://wiki.secondlife.com/wiki/Debug_Help If you're able to capture Fast Timers (I'll be making a how-to on that too) and take a screen capture during a very unstable moment, that might help too. I think to have resolved that issue on my computer!
I did just disabled all overclocking (motherboard + nvidia video card also). Now i'm enjoying SL several hours without crash!  BUT memory leaks are always here  AND all others games (like UT2003 for example) ran always very stable when system was overclocked ! 8o So, I think issue come from layer links beetwens SL viewer and OpenGL 
More infos: People! Please let know when you encouter viewer issues with(out) overclock! Computer: correction: nvidia FX5500 256MO on AGP8X (not 512MB)
i too have the same freezing issues - where can i get 1.13.2.2?
Meta issue. Change this to "meta" state once that's created.
I suffered badly from everything freezing necessitating a comptlete reboot. I have removed my computer side cover. Amount of crashes now a lot, lot less. I conclude an overheating problem. I don't know if it would be the processor or graphics card overheating.
Nova, there's a free program called SpeedFan which let's you monitor CPU temperature and sometimes (depending on the graphics board) GPU temperature also. Btw, I also had reports from two users lately who told me that a broken fan on the video board was causing those kinds of system lockups. hi im twippy,
sounds like in having porbs like you guys.since the updat everything has gone wrong.nothing wont load when im in sl.everything freezes.i have nothing in my inventory.i cant teleport.i have tried reinstaling sl and relogging and clearing cache.how can i get help when sl wont get bk to me thanks twippy I am having the same freeze system or blue screen problem running Second Life on my T60p Lenovo Laptop with a ATI MOBILITY FireGL V5200 video card and two gigs of RAM. People with older laptops do not seem to be suffering from this issue, though they do crash on occasion. Since this laptop was part of a recent issue at my company, a number of my colleagues have run into the same problem and are unable to run Second Life, or like me, unable to run it for very long. It is only a matter of time before Second Life freezes up or crashes. Since updating my bios and drivers (a number of times in order to try and fix this issue), I have been able to extend my ability to run Second LIfe but it is only a matter of time. If I am lucky, it will just die and not freeze the entire computer up (a rare occurrance sadly).
I am able to run Second Life on a home pc built for games and my home mac, and both work just fine. I have to also say, I submitted this as a bug and received the most unhelpful answer (copied below and I only indicate part of the person's name to not embarrass them in public). "Unfortunately your video card, ATI MOBILITY FireGL V5200, is not supported by Second life, we did not test Second life on the FireGL version so I won't be able to tell what you could try to make it works. It is usually a question of finding the right driver for your card. Of course, it could be that the video card on that system is just unable to run Second life properly and different driver won't help. Regards, S_____n Linden" (This was the pathetic attempt at customer service I received after submitting a requested SecondLife.log and DxDiag.txt files as a continuation of my bug and then had it promptly closed. I feel this support person did the bare minimum he/she felt they had to do in order to close the ticket. Since the answer wasn't staring them in the face, they didn't bother to take any more effort. A referral to a tech lead or higher tier I felt would have been in order - or even just a good honest effort by doing a Google search, which is what I resulted to myself, with more possible leads than this support person offered me. I really suggest that Linden Labs either has a chat with their support to make a greater effort. Nearly all major computers are run with either ATI or NVIDIA cards and to suggest that one is just out of luck for having an unsupported card in a recent computer from a major vendor using a mainstream vid card - oh, too bad to be you, is highly unprofessional.) For my fellow Second Life citizens who are using the same machine, any information you can provide on this issue would be helpful. My company is a major presence within SL and my division is trying to come up to speed to see how we might make use of this space, all good efforts to promote the use of Second LIfe. Here is what I found. This freeze problem is very common and widespread on T60 and T60p laptops (again, a simple Google search would have found such). It seems from my Google search that there is a problem with using certain types of memory in Lenovo T60p computers, even with memory that came from the factory. If you are using two sticks of memory, you might be able to resolve this by removing the one causing problems or by disabling the PowerPlay setting for the video card. People have reported that they have fixed this issue by replacing one of the RAM modues. I have tried the latter solution and will update later if I am successful. I am going to order new RAM through our support department to see if that fixes the issue with PowerPlay turned back on and will try to come back here to update as soon as I get any results in either case. Best of luck. S. Laval. In reference to my post above, disabling PowerPlay had no positive effect and SL locked up the entire computer within about 20 minutes. - The issue it seems, at least for earlier T60 and T60p computers, might be related to any OpenGL application. As a test, I installed a graphics-heavy OpenGL gaming application and it froze up the computer in about the same amount of time as SL did. I think I might be having to deal with two similar but separate issues, that of the SL application freezing system and possible memory errors doing same - the latter possibly coming from mismatched RAM from the factory (branded IBM but from two different suppliers).. I found some reports on a gaming site that indicated that matching the RAM or swapping RAM fixed the issue, but these reports were about a year old. So I will attempt my test using both the OpenGL game and SL. If I can get the computer to function in the former but not the latter, I will know that I have at least resolved the hardware issue. In any case, I'll set in motions an attempt to get some different RAM into this machine. I just need to identify which brands might solve this issue and which are to be avoided. My laptop has also been locking up (display is completely frozen, doesn't respond to the mouse or keyboard, if there's music playing, it stutters for a second or two, but then also stops completely). It seems to occur randomly, but seems to happen more often in the act of zooming or moving the camera. I've never had issues with SL on this laptop before the latest version.
Dell XPS M170 sorry - i should have been more specific - dell xps m170 with xp media (all service packs) and 6800 graphics card - i notice a lot of xps m170 laptps appearing here
Could this be a heat/fan issue? Check with speedfan (google) to see if anything shows up. This bug is about something that changed in 1.14.x, not about temperature. The differentiators for this bug are that it did NOT appear in 1.13.x and prior, but DOES appear in 1.14.x and later AND that it hangs the Second Life viewer but NOT other 3D gaming apps. Just as the description says.
Thinkpad T60p, WinXP, latest drivers, ATI MOBILITY FireGL V5200. Since the 1.17 update, I've been experiencing lockups. Often textures begin to waver or turn techni-color, then I lock up. The computer completely freezes. I cannot move the mouse. I cannot use control alt delete. I have to press and hold the power button to reboot. I've taken my computer in to be looked at and had fans cleaned / replaced but the issue still happens as frequently as before. I am on a Toshiba Qosmio with the following specs and updated drivers.
Processor: Intel(R) Centrino(TM) Mobile Technology featuring Display: Toshiba TruBrite(TM) 15.4-inch diagonal TFT System Chipset: Mobile Intel(R) 915PM Express Chipset Graphics Memory: 1024MB DDR SDRAM memory(4) Hard Drive: 100GB 5400 rpm parallel ATA hard disk drive(3) Optical Drive: DVD SuperMulti Double Layer drive Wireless: Intel PRO/Wireless(7) 2200BG (802.11 b/g) Ports: 3 USB 2.0, RGB, S-Video TV out, RJ-45 LAN port, TV Tuner: Integrated Toshiba TV Tuner (US/NTSC) Input Devices: QosmioPlayer (instant-on CD/DVD/TV), Microsoft Slots: 5-in-1 Bridge Media Adapter (Secure Digital(R), Audio: harman/kardon(R) stereo speakers Battery: 6-cell Lithium ion battery (4400 mAh) Operating System: Microsoft(R) Windows(R) XP Media Center Edition i'm no tech man but i tried unticking open gl box and all has been fine since
I also Have this problem, however I have Macs. Apple Macbook Pro 2.2, 2gb, 160gb hd, and Apple G5 quad core, 4GB Mem, 750GB HD, I have three T-1's coming into my place. SL will run for maybe 4-5 minutes and then lock ultimately resulting in my computer(s) to lock.
I have added 1.18 to the affected versions list, as the freezing problem has actually notably deteriorated with these releases. While I have occasionally experienced these freezes since at least 1.16, they were not frequent until 1.18.2. Since then, however, they typically happen more than 20 times a day. While I do not use voice, it may not be a without significance that the overwhelming increase of these freezes coincided exactly with the introduction of voice.
A note on freezing versus crashing, with invitation to confirm: Although the viewer does freeze and inhibit all types of action, including movement, opening and closing windows, and typing in chat and IM, it does not always crash. Sometimes I am able to outwait the freeze until things start working again (this usually takes between 6 and 10 minutes, so most people would probably have rebooted by that time). I have found that running SL with my statistics window constantly open, there is typically a sudden drop in fps down to about 0.3, at which time everything freezes up. If I then try to outwait it, about half the time the minimap turns red and my bandwidth drops to zero, indicating a loss of connection. However, sometimes if I outwait it, functionality will return, beginning with fps increasing to normal levels, followed by restoration of windows/buttons, movement, and chat functionality, in that order, over a period of 6 to 15 seconds. One striking observation is that bandwidth very often remains high during a freeze and actually drops significantly when functionality is restored. I have observed this many times during an unfreeze, so I don't think it's a random quirk. Linking this to
There are still very serious memory leak issues with all Second Life clients. For me, a user with 1 Gig of memory, having Mozilla open with many tabs (multiple web sessions inside a single window), and/or being on Second Life in a sim with a certain number of people nearby, and high of objects and attachments present, will cause SL to crash for me... either the client screen simple disappears and I get the crash-report sending request dialog, or the SL client window goes completely white, and I have to kill the second life client process and start it over again. PLEASE SEE VWR-2997
I'm getting the BSOD about igxprd32. I've already reinstalled the display driver.
Dell Inspiron E1705 Yeah..i thought this was just my computer shitting out for some reason. Especially when I'm trying to build, SL will sputter a bit, saying that SL is not responding, and it takes me like 5 minutes sometimes before it either crashes, comes back, or i have to exit completely. Though, SL has never crashed my computer entirely, just SL itself, while other programs are running just fine. I mean, i'm running Windows XP with an Nvidia 7950GT overclocked, so, I'm sure it's not my hardware. With this info though, I'm not as worried about my computer anymore
 I'm having some variant of this problem with both
Second Life 1.18.4 (3) Nov 7 2007 11:13:48 (Second Life Release) CPU: Intel Core 2 Series Processor (2327 MHz) and Second Life 1.18.5 (74061) Nov 19 2007 10:10:17 (Second Life WindLight) CPU: Intel Core 2 Series Processor (2327 MHz) While the viewer is running, the entire machine will freeze, requiring a hard power-off reboot. Sometimes, if I wait long enough, I will get a "device driver went into an infinite loop" BSOD, but generally the screen just stops changing entirely, and nothing works except mouse movement (and usually that eventually stops working also). Sometimes it happens during the "Downloading clothing" part of login, sometimes it happens just as the viewer is rendering the first few frames of the new session (nicely losing all the pending IMs and notices before I have a chance to see them), sometimes it happens during the session. It often seems to happen while I'm camming around, but since I'm usually camming around that may not mean anything. I've had this with many previous versions of the viewer (all of them, really), but it's gotten MUCH worse lately. I've been playing lots of WoW, sigh... I will attach the SecondLife.log from a recent one of these crashes, as SecondLife_DaleInnis_1.log. The last line in it is 2007-11-28T15:56:52Z WARNING: LLAudioChannelFMOD::cleanup error: An invalid parameter was passed to this function which may or may not mean anything. (Voice was not active when this crash occurred; I almost never use voice.) Please please fix; WoW is a poor substitite for SL, or it would be if I could run SL without knowing that the entire machine was probably going to lock up... /me cries. I turned various graphics options way down and had one good crashless session (very unusual!), but the next time I ran the viewer (1.18.5 now) it hung immediately after displaying the hated "Your clothing is still downloading" popup (before I could even press "OK"). Log SecondLife_DaleInnis_2.log attached.
My hardware configuration is like Dale Innis' and I'm having the same problems.
However, I have noticed some places where this tends to be worse. When I TP or login to a spot that has a high number of textures/objects that overlap it is much worse. Some additional information follows: The BSOD occured in ATI2MTAG until I uninstalled QuickTime then it became ATI2DVAG. Partially transparent textures tend to overlap everything else. Often, the BANDWIDTH with the servers spike at the freeze. Right off the screen. Could there be an issue with z-indexing alpha textures? Update on the last few days/weeks of crashes: Recently I've had very very few machine lockups while inworld. The viewer itself did crash once while I was inworld, but without locking the machine.
On the other hand, I've had many many many machine lockups when first logging in; I'd say the machine locks up more than half the time that I start the client. It almost always occurs when the bar is full or nearly full at "precaching", when the "precaching" bar as vanished and the "downloading clothing" bar hasn't yet appeared, when the "downloading clothing" bar is somewhat full, or when the "your clothing is still downloading" popup appears (in the latter case, I can't click "OK" on the popup). Things I have tried include: clearing cache (either via the client or via Windows "rmdir /s" on the cache directory before starting the client), logging in at different places (home vs. last location vs. a named region), using the current mainline client v. the current WindLight client. None of these seem to help in any patterened way; I almost always clear cache one way or another, but I still get the machine hang more than half the time. Logging in here rather than there, or in Windlight rather than not, still seems to hang the machine just as often. On the other hand, after trying enough times I do manage to get in eventually. No idea what's making the difference. Let me know if yet more logs would help or anything. Just in case, I'll upload one where the machine hung during startup of the Windlighth viewer, when I had (I believe) removed the cache by hand with rmdir before starting the viewer. See SecondLife_DaleInnis_3.log. Machine (Lenovo Thinkpad T60) hung solid during startup of Windlight viewer, when I had (I believe) brute-force cleared cache with rmdir /s before starting the viewer.
Second Life 1.18.3 (5) Sep 20 2007 11:41:23 (Second Life Release)
DELL Latitude D820 Laptop Was working fine earlier today. I logged out and then relogged in, went to NORTHSTAR shopping mall. Problem with igxprd32 Also sent a Crash Report. Graphics Card: Intel 945GM
Since update to 1.19.1 (4) no more blue screens and only crashed one time! This update craves for RAM tho, but no more blue screens is deff a thumbs up! There are several reasons why I am updating this issue. As noted above, I thought that renaming it "freezelag" would provide a more comprehensive description of the issue it seems to cover and, in particular, acknowledge the fact that some freezes are not fatal--they spontaneously recover (at least temporarily, until they happen again 3 to 5 minutes later) without necessarily crashing the viewer or requiring a reboot.
The second reason is to update and confirm that the issue still affects version 1.19.1.4 of the SL viewer :/ The third reason is that I have accidentally stumbled upon a very unexpected and extremely counterintuitive effect related to freezelag that (1) could be useful as a workaround and (2) might give someone with a more technical background than myself a clue to possible underlying causes. To briefly recap, my personal experience with freezelag ever since the introduction of voice has basically been as follows: for a certain period of time A, the viewer works fine at a framerate of about X, allowing me to function normally in-world. Then without warning, the framerate drops to a catastrophically low value Y for a period of time B. If by the end of B the viewer has not redmapped or crashed, fps rise again to a more civilized value for the next period A, then the process repeats. The values of A, B, X, and Y have varied across different versions of the SL viewer: in 1.18.3.5, A was usually between 15 and 20 minutes, B was 3 to 4 minutes, X was about 8 to 10 fps, Y was about 0.4 fps. In 1.19.1.4 (voice disabled), A is rarely more than 5 minutes, B is typically at least as long as A!! (much longer than 5 minutes occurs but usually leads to a loss of connection), X is about 20 to 25 fps, Y is best expessed in seconds per frame and can drop as low as 90 spf, though the average is closer to 10 spf. It will be apparent that an inverse relationship seems to exist between peak framerates and frequency of freezelag: the higher the peak fps, the quicker freezelag occurs. Likewise, higher fps peaks seem to correlate with deeper dips in fps. Thus, although 1.19.1.4 shows an improvement of my peak framerates to about 25 fps, the troughs of intermittent freezelag are correspondingly longer and deeper (0.1 fps or less). Nothing else seems to be strongly correlate to this recurrent freezelag except time in world (which suggests a possible correlation with the ubiquitous memory leak). There are weak correlations with such load related measures as the number of scripts or the number of agents in the region, but on the whole these have only a minor impact compared to the steady rhythm of freezelag you can practically set your clock by. Or at least I thought so until two days ago. Mindnumbingly counterintuitive though it may seem, I recently discovered a strong correlate that turns out to be remarkably effective in comparison to anything else I have tried !Unable to render embedded object: File (>>> Running multiple instances of the SL client *reduces* deep freezelag <<<) not found.! I am not kidding! I discovered this quite by accident two days ago. When the 1.19.1.4 client became "mandatory," I installed it but kept a backup version of 1.18.5.3 so I could switch back if 1.19 turned out to be too buggy. As noted above, while peak framerates improved in 1.19, freezelag troughs likewise deepened and lengthened. Two days ago, I accidentally launched my backup 1.18.5.3 while I was already running 1.19.1.4. Rather to my surprise, this did not crash me as it usually had in the past, so I decided I might as well log in one of my alts to compare performance. I was very surprised at the result. Simply put, running two viewers (of different versions, which may be important) at the same time "smoothed out" my freezelag: my peak framerate dropped to about 8 fps, but at the same time my lag troughs shallowed to about 3 fps, which is not exactly ideal, but it sure beats 20-second stills. At the cost of a lower peak framerate, the inhumanly slow framerate of freezelag became more bearable--a tradeoff I personally found more than worthwhile. I am not enough of a geek to begin imagining what this means, but one thing I am pretty sure about: whatever causes the grinding several-seconds-per-frame freezelag that poisons my SL experience and seems to at least occasionally affect nearly every resident I have met, it is not simply linearly related to load (other causes of lag may be, but the deep 0.3 fps or worse freezelag is not). Running more than one copy of the viewer at the same time is surely a heavier load on any computer than running a single copy of the viewer, AND YET THE REALLY DEEP FREEZELAG SHALLOWS OUT WHEN THIS EXTRA LOAD IS IMPOSED. It may be of significance that I found this while running two different versions of the viewer (which maybe use certain resources differently?). It surely must mean something that the deepest dips in fps improve even as the sharpest peaks of fps deteriorate. Perhaps the worse performance of 1.19 in terms of more frequent freezelag is literally the price we pay for the higher peak framerates that 1.19 unquestionably shows. I do hope most fervently that this strikingly counterintuitive observation may give a clue that could pave the way for the eventual resolution of this problem. The small print: Dell laptop, Intel 1.33 Ghz single core, 1,024 MB RAM, ATI Radeon, Windows XP, cable modem, Roadrunner Since updating both the video drivers and the view (to 1.19), I've had many many fewer instances of the entire system crashing (touch wood) requiring a reboot. The viewer itself still crashes occasionally, but even that is rare.
On the other hand I've begun experiencing more of what Veronica calls "freezelag", where the FPS rate suddenly crashes from a normal value to something significantly less than one (as in, two or three or more seconds pass between screen updates, which because of the client's threading model means that two or three or more seconds pass between opportunities for me to do anything, including typing in chat). For me, freezelag usually happens when there are a significant number of AVs around; doesn't have to be dozens: any number more than about four seems to be able to do it. Sometimes turning off prim rendering (c-a-s-9) raises FPS again, sometimes turning off AV rendering (c-a-s-4) does it, and turning off both pretty much always raises FPS (although of course if I can't see AVs or prims, all I can really do is chat and IM). I'll have to try the two-client-processes trick and see if that does anything... Fwiw... Showing how RenderGeom dominates time when in freezelag mode. Bottom half of the plot is with prim rendering off (c-a-s-9, around 10 fps), top half is with prim rendering on (around 0.5 fps).
Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release) CPU: Intel Core 2 Series Processor (2327 MHz) To expand slightly on the screenshot comment: I'm still having this problem in the latest release viewer. Last night it happened when there were only a small number of AVs around, and I was sitting in a place where the fps had been just fine until suddenly it dropped to less than one without anything obvious changing in the world to trigger it. Turning off prim rendering with control-alt-shift-9 brought fps up again, as it usually does. Turning on the control-shift-2 timers produced the screenshot, showing that nearly all of the rendering time when freezelagging is in RenderGeom.
Any suggestions of other things to try, other data to gather, or things that might be causing this, would be most welcome! At someone's suggestion, I moved my graphics memory size (in preferences / graphics / hardware settings or whatever) from 512 (the max on my slider, where it was) to 256, and the problem seems to have gone pretty much away. Very strange!
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Meta Issue
Reopened
Critical
Meta-Issue: Freezelag (sometimes but not always crashing viewer or requiring reboot)
