Page MenuHome

Clicking on Shader tab causes crash
Closed, DuplicatePublic

Description


System Information
Operating system: Windows 10, v 1903, Build 18362.239
Graphics card: Nvidia 980Ti, Driver version: 431.60 (current)

Blender Version
Broken: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e
Worked: (optional)

Fresh install, open to default project (cube). Select Shader workspace tab and crash to desktop.

Using the default startup, no additional plugins.

Also tried:

32bit version, still crashed
Starting under Administrator, still crashed
Runs fine as a VMware Guest..

Event Timeline

Some more info..

Using the latest NVIDIA drivers. (431.60)

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF61352FAA0
GL API other: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast).
Module : C:\Program Files\Blender Foundation\BlenderBeta\blender.exe
GL API

Ed H. (Ed-H) renamed this task from Clicking on Shader tab causes crash (NVIDIA) to Clicking on Shader tab causes crash.Oct 6 2019, 5:37 AM

Still crashes.

Started Blender
Loaded factory settings
Clicked on the Shader tab. Session closes Immediately to the desktop

Nvidia driver 441.41

ronsn added a subscriber: ronsn.Dec 22 2019, 10:11 PM

@Ed H. (Ed-H) does this issue also occur if you first select the Material preview (see Screenshot) and after that switching to the Shading workspace?

Yes. No difference.

in the Blender folder should be 4 different *.cmd files. Can you start one of the other, replicate the error, paste debug_logs to https://developer.blender.org/paste/ and link them to this ticket ?

Done, See "T68164 - Blender 2.8x clicking on Shader tab causes crash"

sorry I meant "Can you start one after the other, replicate the error,...". Do all four of them give the same debug_log ? (after each run you need to save it somewhere)

Then juste paste the "pastenumber" here, like that: P1195

P1195 has been updated with the requested information.
Thank you

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Developer to Reproduce.Dec 30 2019, 5:19 PM

From the log I can see that the crash occurs in the blender.exe module.
So even if the source of the problem is from the NVidia driver, the crash occurs somewhere in blender code itself.
It may be the result of some corrupted memory or some invalid NULL return.
But it is very difficult to know what is happening without a developer who can reproduce the problem.

Maybe with the D3576: Crashpad support we could identify more exactly where the crash occurs.