Cool VL Viewer forum

View unanswered posts | View active topics It is currently 2024-03-28 23:54:10



Reply to topic  [ 6 posts ] 
Crash with AMD Driver 20.10.1 
Author Message

Joined: 2011-10-07 10:39:20
Posts: 181
Reply with quote
Hi Henri,

i saw a crash with the "improved OpenGL" performance branch of the AMD driver.

The stacktrace leads deep into the driver, so i guess there is not much to do there.

It seems there is some problem when the scene is full, like Frogmore (https://maps.secondlife.com/secondlife/Koro/10/143/24), the viewer exploded to like 12-14GB of RAM and froze without any interactions after walking around a little. Reducing the texture decode threads to just 2 didn't help, and draw distance was just 64m.

I guess the driver isn't stable yet. I tried with Firestorm and it did not have this crash behaviour (or i got lucky).

Kathrine


Attachments:
logs.zip [38.3 KiB]
Downloaded 26 times
2022-10-11 15:36:57
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
Try reducing the maximum bound memory (MaxBoundTexMem) debug setting to 2048MB, in case the driver would eat up more memory than what the viewer expects it to do.


2022-10-11 15:41:24
Profile WWW

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
Went there, and the viewer never ate more than 8.5GB of RAM, with 512m draw distance and all graphics maxed out (excepted no shadows), but the GL bound tex memory did overshoot briefly my default limit (2560MB) while moving around, at the village center... If AMD's driver leaks memory, that could explain the crash around here...

Attachment:
TheShambles.jpg [688.8 KiB]
Not downloaded yet


2022-10-11 15:55:15
Profile WWW

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
I had a look at your crash dump, but it points at "atio6axx.dll", and no stack frame is shown for calls in the Cool VL Viewer itself (the address of the crash points into a Win64 worker thread used by the driver's DLL), and is therefore not even the direct result of a GL call by the viewer...
Attachment:
CrashDumpAnalysis.jpg [299.81 KiB]
Not downloaded yet

It means there is strictly nothing I can do, and you should report that crash to AMD so that they fix their driver...


2022-10-11 17:06:26
Profile WWW

Joined: 2011-10-07 10:39:20
Posts: 181
Reply with quote
Ok, thank you. I'll see if i can find something myself and reported the crash to AMD.

By the way, you know that both NVidia and AMD publish the symbol files for the drivers:

https://developer.nvidia.com/nvidia-dri ... bol-server
https://gpuopen.com/learn/amd-driver-symbol-server/

So the crash is somewhere in the depths of eglGetProcAddress(), but only AMD should be able to figure out why.


2022-10-12 12:47:50
Profile

Joined: 2009-03-17 18:42:51
Posts: 5523
Reply with quote
Thanks for the links.


2022-10-12 14:22:50
Profile WWW
Display posts from previous:  Sort by  
Reply to topic   [ 6 posts ] 

Who is online

Users browsing this forum: Mr.Tach and 18 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software.