Page MenuHome

Blender 2.80 (sub 39): Crashes at Shading tab
Closed, ArchivedPublic

Description

System Information
Operating system: Windows 7 x64 OEM Ultimate with SP1
Graphics card: ATI Radeon HD7650M
Blender Version
Broken: blender 2.8, 8839152abf5, build 2018-12-18 13:27
Worked: (optional)

Blender crashes down when clicking Shading tab. Remaining tabs is still working.
«
Microsoft Visual C++ Runtime Library:
Runtime Error!
Program: D:\blender-2.80-8839152abf5-win64\blender.exe

R6025

  • pure virtual function call

»
After crashing, blender.exe continues displaying in Task Manager until being forced to shut down.
Full system info is included in system-info.txt

Event Timeline

Jacques Lucke (JacquesLucke) lowered the priority of this task from 90 to 30.Dec 19 2018, 11:15 AM

Please start Blender from the console, reproduce the crash and then post the output here.

PATH\\TO\\blender.exe --debug --debug-gpu

I'm having same problem.



Jacques Lucke (JacquesLucke) raised the priority of this task from 30 to 90.Dec 19 2018, 2:47 PM
Frederic (Gol) added a comment.EditedDec 19 2018, 4:58 PM

Actually reproduced the crash with --debug --debug-gpu and CLI window sink. Also added userprefs.
Looks like this is caused by ATI GPU driver itself, because Blender doesn't use Visual C++.

I'm having same problem.

Yeah, I also can't figure out how to disable this soapy line smoothing in Radeon settings. The quality and anisotropic filtering settings doesn't affect anything.

Frederic (Gol) added a comment.EditedDec 23 2018, 4:53 AM

Upd. I just tried to use Linux build of the Blender (build 4c5e76025d83) on Linux Mint 18.2, and tried to reproduce. However, no crashes happened, it works! Oohooh my god, it's craazy! Love this so much!


I also noticed that orange outlines on the selected objects looks well and smooth, compared to how crispy it rendered in the Windows, as described above (this actually happens in every OpenGL app rendered in Windows with discrete ATI GPU driver, including fonts and 2D objects looked soapy too).

Conclusion: AMD Radeon Mobile Series drivers for Windows really suxx. And, sadly, everyone who uses them most likely will not able to use all Blender EEVEE and Shading capabilities until switching to Linux, or using computer with better graphic card.

@Frederic (Gol) vista or windows 7 .. sux... with these video cards or drivers ..
anyway now the problem has been dammed on windows, (windows 10 is better)
it's performance is at least three times higher than linux ..

on linux ..I would hope they can achieve similar results ..
this situation had been improved about a month ago .. with the last mesa - devel ..
but now changes have been made and shadow ESM and VSM and Lights no longer work ...
follow this bug report .. for detailed information ..
let's see if we solve this problem
https://developer.blender.org/T60001

Frederic (Gol) added a comment.EditedJan 5 2019, 12:06 PM

I had now downgraded my AMD driver from ver. 17.(...) to version 15(...). As it was recommended by the Catalyst app. And, surprisingly, it solved the problem with the crash and with soapy outline rendering!


So everyone who has the same problem, try to change the driver version or downgrade to the most stable or recommended version.

Thanks! Older driver version for me also resolved the issue (for both reportd Blender version and a current one, at a time of writing this).

In my case driver downgrade was ver 14. to 13. (AMD FirePro M7820 on a almost 10y old HP laptop:).

A side note: old and discontinued hardware is not recommended for realtime GPU shading.

Jacques Lucke (JacquesLucke) changed the task status from Unknown Status to Unknown Status.Jan 22 2019, 10:52 AM
Jacques Lucke (JacquesLucke) claimed this task.

I had now downgraded my AMD driver from ver. 17.(...) to version 15(...). As it was recommended by the Catalyst app. And, surprisingly, it solved the problem with the crash and with soapy outline rendering!

Older driver version for me also resolved the issue

@Clément Foucault (fclem): looks like sometimes having the newest driver is not the best choice..

im on macbook and i dont really understand how to reproduce it? so could someone explain how to fix it please