search

secondlife / jira-archive

2 stars 0 forks source link

[BUG-7727] Crash upon camming or turning avatar in busy region. #15402

Open sl-service-account opened 9 years ago

sl-service-account commented 9 years ago

Steps to Reproduce

Camming/turning.

Actual Behavior

Basically, if you go to a busy region (more than 10 avatars), sit for a spell, and then turn or cam around. The client hits the disk VERY hard and crashes. It doesn't seem to matter what your graphics settings are set at, even if the number of avatars rendered is set to 8 or so, it still happens. Happened on my old GT220 too.

Expected Behavior

To not crash.

Other information

This one has gotten worse. I don't remember it being in older parts of the 3.x.x series clients.

Attachments

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-7727 | | Summary | Crash upon camming or turning avatar in busy region. | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | CronoCloud Creeggan (cronocloud.creeggan) | | Created at | 2014-11-07T03:36:37Z | | Updated at | 2015-06-19T04:34:54Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2014-11-07T10:30:53.223-0600', "Is there anything you'd like to add?": "This one has gotten worse. I don't remember it being in older parts of the 3.x.x series clients.", 'Regression?': ['Issue is a Regression'], 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': "Basically, if you go to a busy region (more than 10 avatars), sit for a spell, and then turn or cam around. The client hits the disk VERY hard and crashes. It doesn't seem to matter what your graphics settings are set at, even if the number of avatars rendered is set to 8 or so, it still happens. Happened on my old GT220 too.", 'What were you doing when it happened?': 'Camming/turning.', 'What were you expecting to happen instead?': 'To not crash.', 'Where': 'http://maps.secondlife.com/secondlife/Floris/44/126/502', } ```
sl-service-account commented 9 years ago

Whirly Fizzle commented at 2014-11-07T16:30:53Z

I suspect you are getting out of memory crashes. I can easily reproduce this too on the Linden viewer (or any 32 bit viewer) and your repro is exactly how I force an out of memory crash when I want to get one for testing something. Go to a busy region and cam about a lot.

On my system (Windows 7, 64bit) I can reproduce an out of memory crash in this way within 10 - 20 minutes of logging in on a busy region and camming. On a 32 bit system it was much worse, I could reproduce it within 2 minutes.

The next time you reproduce this crash, can you zip up your logs folder and attach it to this issue using More Actions -> Attach files. This page tells you where to find the logs folder: http://community.secondlife.com/t5/English-Knowledge-Base/How-to-report-a-bug/ta-p/733545#Section_.3

sl-service-account commented 9 years ago

CronoCloud Creeggan commented at 2014-11-12T15:12:42Z

updated with logs from this crash. I am running 64 bit with 4GB of RAM as you can see. Does it still happen with one of the 64-bit TPV builds?

sl-service-account commented 9 years ago

Whirly Fizzle commented at 2014-11-13T01:50:58Z

Hmm the log session just cuts dead without registering a crash. This can happen if the system freezes or the graphics driver crashes though.

Theres some strange memory stuff going on just before you crash - I dont know if these lines are anything bad though, but I dont recall seeing them before...

2014-11-12T15:06:17Z WARNING: Request: VFS write to temporary block (shouldn't happen)
2014-11-12T15:06:17Z WARNING: Request: VFS write to temporary block (shouldn't happen)
2014-11-12T15:06:17Z WARNING: Request: VFS write to temporary block (shouldn't happen)
2014-11-12T15:06:17Z WARNING: Request: VFS write to temporary block (shouldn't happen)
2014-11-12T15:06:17Z WARNING: Request: VFS write to temporary block (shouldn't happen)
2014-11-12T15:06:17Z WARNING: Request: VFS write to temporary block (shouldn't happen)
2014-11-12T15:06:17Z WARNING: Request: VFS write to temporary block (shouldn't happen)
2014-11-12T15:06:17Z WARNING: Request: VFS write to temporary block (shouldn't happen)
2014-11-12T15:06:17Z WARNING: Request: VFS write to temporary block (shouldn't happen)
2014-11-12T15:06:17Z WARNING: storeData: VFS: Attempt to write to invalid block in file 1bd9dcd9-fc48-307d-7175-5f9ee1227a14 location: -1 bytes: 1000
2014-11-12T15:06:17Z WARNING: storeData: VFS: Attempt to write to invalid block in file 1bd9dcd9-fc48-307d-7175-5f9ee1227a14 location: -1 bytes: 1000
2014-11-12T15:06:17Z WARNING: storeData: VFS: Attempt to write to invalid block in file 1bd9dcd9-fc48-307d-7175-5f9ee1227a14 location: -1 bytes: 1000
2014-11-12T15:06:17Z WARNING: storeData: VFS: Attempt to write to invalid block in file 1bd9dcd9-fc48-307d-7175-5f9ee1227a14 location: -1 bytes: 1000
2014-11-12T15:06:17Z WARNING: storeData: VFS: Attempt to write to invalid block in file 1bd9dcd9-fc48-307d-7175-5f9ee1227a14 location: -1 bytes: 1000
2014-11-12T15:06:17Z WARNING: storeData: VFS: Attempt to write to invalid block in file 1bd9dcd9-fc48-307d-7175-5f9ee1227a14 location: -1 bytes: 1000
2014-11-12T15:06:17Z WARNING: storeData: VFS: Attempt to write to invalid block in file 1bd9dcd9-fc48-307d-7175-5f9ee1227a14 location: -1 bytes: 1000
2014-11-12T15:06:17Z WARNING: storeData: VFS: Attempt to write to invalid block in file 1bd9dcd9-fc48-307d-7175-5f9ee1227a14 location: -1 bytes: 1000
2014-11-12T15:06:17Z WARNING: storeData: VFS: Attempt to write to invalid block in file 1bd9dcd9-fc48-307d-7175-5f9ee1227a14 location: -1 bytes: 190
2014-11-12T15:06:17Z WARNING: downloadCompleteCallback: downloadCompleteCallback has non-existent or zero-size asset 355742df-d116-22a2-7cd4-e64c78dfa750
sl-service-account commented 9 years ago

Whirly Fizzle commented at 2014-11-13T01:52:44Z

Just before the log cuts dead, memory reading is...

2014-11-12T15:06:52Z INFO: display_stats: MEMORY: 0 MB
2014-11-12T15:06:52Z INFO: logMemoryInfo: Current allocated physical memory(KB): 1003KB

That looks suspicious... 1003KB is very low.

sl-service-account commented 9 years ago

CronoCloud Creeggan commented at 2015-06-17T13:12:06Z

If anything this one has gotten worse since November.

sl-service-account commented 9 years ago

CronoCloud Creeggan commented at 2015-06-19T04:34:55Z

something interesting is happening now. The viewer locks up with heavy disk activity, and heavy CPU activity, but then eventually I get the "darn you've been logged out of second life, the region you're in, etc etc." but the region I was in isn't having issues.