Crash when changing the engine to Eevee #53089

New Issue

Germano Cavalcante · 2017-10-17T04:30:38+02:00

2017-10-17 04:30:38 +02:00

System Information
Windows 10 - 64bits
renderer: AMD Radeon HD 7500M/7600M Series
openGL version: 4.5.13399 Core Profile Context 0

Blender Version
Blender 2.8
hash: 8ffb761387

Short description of error
If you change the engine from Eevee to Clay or Cycles and then return to Eevee, a Crash with the following message occurs:
Exception thrown at 0x000000006E216906 (atio6axx.dll) in blender.exe: 0xC0000005: Access violation reading location 0x0000000000000008. occurred

The same does not happen if you change the engine to Blender Render and go back to Eevee. You must have started Cycles or Clay at least once.

Here an image showing the call stack:

And here's the backtrace:
blender.crash.txt

**System Information** Windows 10 - 64bits renderer: `AMD Radeon HD 7500M/7600M Series` openGL version: `4.5.13399 Core Profile Context 0` **Blender Version** Blender 2.8 hash: 8ffb76138731d6241a6ac5bfc17bb764cfa59053 **Short description of error** If you change the engine from `Eevee` to `Clay` or `Cycles` and then return to `Eevee`, a Crash with the following message occurs: ```Exception thrown at 0x000000006E216906 (atio6axx.dll) in blender.exe: 0xC0000005: Access violation reading location 0x0000000000000008. occurred``` The same does not happen if you change the engine to `Blender Render` and go back to `Eevee`. You must have started `Cycles` or `Clay` at least once. Here an image showing the call stack: ![call_stack.png](https://archive.blender.org/developer/F1042465/call_stack.png) And here's the backtrace: [blender.crash.txt](https://archive.blender.org/developer/F1042467/blender.crash.txt)

Germano Cavalcante commented

2017-10-17 04:30:38 +02:00

Changed status to: 'Open'

Germano Cavalcante commented

2017-10-17 04:30:38 +02:00

Added subscriber: @mano-wii

Clément Foucault was assigned by Germano Cavalcante

2017-10-17 04:31:18 +02:00

Joshua Leung commented

2017-10-17 06:10:26 +02:00

Added subscriber: @JoshuaLeung

Joshua Leung commented

2017-10-17 06:10:26 +02:00

@mano-wii
Could you try running blender with the --debug-gpu and --debug-gpu-shaders and report any errors that come up from those? IIRC, in previous cases of crashes, it's been due to the drivers/GLSL compilers not liking some or other construct in the shaders.

@mano-wii Could you try running blender with the --debug-gpu and --debug-gpu-shaders and report any errors that come up from those? IIRC, in previous cases of crashes, it's been due to the drivers/GLSL compilers not liking some or other construct in the shaders.

Germano Cavalcante commented

2017-10-17 07:29:52 +02:00

@JoshuaLeung
Good sugestion. The generated log seems very clear :)
After much and much line, there is this part:
debug-gpu-log.txt

@JoshuaLeung Good sugestion. The generated log seems very clear :) After much and much line, there is this part: [debug-gpu-log.txt](https://archive.blender.org/developer/F1042619/debug-gpu-log.txt)

Clément Foucault commented

2017-11-01 16:15:26 +01:00

Changed status from 'Open' to: 'Resolved'

Clément Foucault closed this issue

2017-11-01 16:15:26 +01:00

Clément Foucault commented

2017-11-01 16:15:26 +01:00

Fixed by removing unecessary downsampling of minzbuffer in 345ffe3e4d.

Cause of the issue is still uncertain.

Fixed by removing unecessary downsampling of minzbuffer in 345ffe3e4d9f. Cause of the issue is still uncertain.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crash when changing the engine to Eevee #53089