• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: VWR-8944
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: WorkingOnIt Linden
Reporter: norritt Xi
Votes: 4
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
1. Second Life Viewer - VWR

Second Life Client crashes on logout.

Created: 31/Aug/08 05:29 PM   Updated: 14/Mar/09 08:41 PM
Return to search
Component/s: None
Affects Version/s: 1.20, 1.21 Release Candidate
Fix Version/s: 1.22

Environment:
Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release)

You are at 266427.2, 290609.9, 23.2 in Insula Inferi West located at sim3533.agni.lindenlab.com (216.82.22.14:12035)
Second Life Server 1.24.3.95195

CPU: Intel Core 2 Series Processor (2666 MHz)
Memory: 2815 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 9800 GTX/9800 GTX+/PCI/SSE2
OpenGL Version: 2.1.2
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.17762 (Mozilla GRE version 1.8.1.13_0000000000)
Packets Lost: 103/204035 (0.1%)
Issue Links:
Duplicate
 
Relates
 

Linden Lab Issue ID: DEV-21991
Linden Lab Internal Branch: viewer_1-22


 Description  « Hide
Both the regular Second Life 1.20.15 viewer as well as the 1.21 RC0 crash on logout since I've updated to nVidia GeForce 177.79 drivers. These crashes did _not_occur with GeForce driver version 175.19. Unfortunately it is impossible to provide a crash log to this issue because the client crashes due to a memory access violation and is terminated by the operating system at once. The watchdog doesn't jump in and no crash data is being sent. The good thing about the bug is, it is perfectly reproducable:

1. Install either the current regular viewer (1.20.15) or the 1.21 RC0 on a similar system as described in the "Environment" text box.
2. Log into Second Life.
3. Log out and see the client crash with a memory access violation.

Expected behaviour:
Client shuts down and is terminated without throwing an exception.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Maggie Darwin added a comment - 02/Sep/08 05:33 AM
I've seen this behavior too.

Maggie Darwin added a comment - 18/Sep/08 10:31 AM
On 1.21 RC2 it fails 100% of the time.

Alexa Linden added a comment - 25/Sep/08 10:49 AM
Hi Norritt! Can you or anyone please attach a crash report?

norritt Xi added a comment - 26/Sep/08 05:06 PM
Hi Alexxa,

we can not provide more information on this bug. As I wrote in the description the crash is caused by a memory access violation. This means either SL or the latest nVidia driver try to access a memory adress they aren't allowed to access. Therefore the process is killed by the operating system - Windows XP in my case - before SL or the watchdog can kick in and collect any data. So no one will ever be able to send a report /log on this crash. I suggest you forward this issue to QA, and they install the nVidia GeForce 177.79 on a "Wintel" system and just repro the issue themselves. Maybe it is a good idea to ask Zen to contact nVidia. Since the problem didn't occur with the 175.16 drivers this seems to be at least somehow driver related. Prolly it has to do with the PhysX support, that was added by nVidia in the latest release. However it is not completely nVidias task to track that issue since I only observed this behaviour with SL but not with other 3D-Apps / Games.


Maggie Darwin added a comment - 07/Oct/08 05:24 PM
Still failing on RC 4 and RC 5 ....in fact if you're not careful it can interfere with installing RC 5; if you let the old client do the download of the new and tell it to terminate the running viewer, tt raises a crash dialog that keeps the files open, preventing the new viewer from installing until you dismiss it.

Ramzi Linden added a comment - 08/Oct/08 11:51 AM
Thanks for reporting this. We'll investigate.

Ramzi Linden added a comment - 21/Nov/08 10:41 AM
We believe we have this fixed in version 1.22, which is currently in its Release Candidate phase. (However 1.22 RC0 may be more crashy in general at its early iteration. However, this specific crash at logout should no longer occur.)