crash when changing viewport shading to wireframe mode #87970

New Issue

Diogo Valadares Reis dos Santos · 2021-05-01T19:21:47+02:00

Diogo Valadares Reis dos Santos commented

2021-05-01 19:21:47 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14760 Core Profile Context 21.2.3 27.20.14535.3005

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-04-23 20:25, hash: 17fca62fff, type: Release
Broken: 2.81
Worked: 2.80

Short description of error

if you have a high poly mesh and try change the shading mode to wireframe. depending on the model it constantly crashes.

Exact steps for others to reproduce the error

I noticed this trying to make a retopo of a character. I tried to check what was causing de crash by deleting each object and testing the wireframe.

I deleted everything but the main body mesh, without any uv map, vertex color or any other thing that could make it heavier, and also I tried reseting factory settings.

I would send the file but its 200mb, the main mesh has about 4million vertices.

the crash doesn't happen when changing to eevee or solid view, it only happens when changing to wireframe.

Important note: if you DON'T move the camera after opening the file before changing to wireframe it doesn't crash even if you go to solid and wireframe back and forth as shown in the video bellow
2021-05-01 14-18-16.mp4

blender_system_info.txt
blender_debug_output.txt
untitled.blend

open the file above
rotate it about 180degrees
activate wireframe

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14760 Core Profile Context 21.2.3 27.20.14535.3005 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-04-23 20:25, hash: 17fca62fff9b, type: Release Broken: 2.81 Worked: 2.80 **Short description of error** if you have a high poly mesh and try change the shading mode to wireframe. depending on the model it constantly crashes. **Exact steps for others to reproduce the error** I noticed this trying to make a retopo of a character. I tried to check what was causing de crash by deleting each object and testing the wireframe. I deleted everything but the main body mesh, without any uv map, vertex color or any other thing that could make it heavier, and also I tried reseting factory settings. I would send the file but its 200mb, the main mesh has about 4million vertices. ![image.png](https://archive.blender.org/developer/F10048897/image.png) the crash doesn't happen when changing to eevee or solid view, it only happens when changing to wireframe. Important note: if you DON'T move the camera after opening the file before changing to wireframe it doesn't crash even if you go to solid and wireframe back and forth as shown in the video bellow [2021-05-01 14-18-16.mp4](https://archive.blender.org/developer/F10048906/2021-05-01_14-18-16.mp4) [blender_system_info.txt](https://archive.blender.org/developer/F10051806/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F10051807/blender_debug_output.txt) [untitled.blend](https://archive.blender.org/developer/F10051747/untitled.blend) - open the file above - rotate it about 180degrees - activate wireframe

Diogo Valadares Reis dos Santos commented

2021-05-01 19:21:47 +02:00

Added subscriber: @Diogo_Valadares

Diogo Valadares Reis dos Santos commented

2021-05-01 19:38:22 +02:00

I just checked some bug reports and it seems like i'm not the only one having this issue
#87741, #85860, #84841,#85674,#79749,#80041

I also just tested it and it crashes even in the 2.83 lts in the exact same way, it only crashes if you move the camera before entering wireframe mode... in fact, this bug goes way back to blender 2.81, before that in blender 2.80 it doesn't happen.

Also I noticed that rotating the camera just a little bit or zooming with scroll wheel doesn't make it crash

I just checked some bug reports and it seems like i'm not the only one having this issue #87741, #85860, #84841,#85674,#79749,#80041 I also just tested it and it crashes even in the 2.83 lts in the exact same way, it only crashes if you move the camera before entering wireframe mode... in fact, this bug goes way back to blender 2.81, before that in blender 2.80 it doesn't happen. Also I noticed that rotating the camera just a little bit or zooming with scroll wheel doesn't make it crash

Germano Cavalcante commented

2021-05-03 16:22:15 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2021-05-03 16:22:15 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Germano Cavalcante commented

2021-05-03 16:22:15 +02:00

Is it possible to replicate the crash using a mesh with a subsurface modifier?
Although the crash log is useful, it does not replace the steps to reproduce the bug.
It is possible that the file is corrupted or an addon such as cats-blender-plugin-master is causing this.

Is it possible to replicate the crash using a mesh with a subsurface modifier? Although the crash log is useful, it does not replace the steps to reproduce the bug. It is possible that the file is corrupted or an addon such as `cats-blender-plugin-master` is causing this.

Diogo Valadares Reis dos Santos commented

2021-05-03 19:54:34 +02:00

The problem with this bug is that I don't really think its easily reproducible, I'm pretty sure I already got this many times, whenever I finish a sculpt and start the retopo, when I go to wireframe it crashes.

I tried remake what I did to the model before: I used boolean,multiresolution, regular subdivision, increased the poly count to 8 million, tried to use dyntopo but any of those seems to make a difference.

The problem seems to be directly related to the wireframe, it also crashes if I activate the wireframe in the solid mode overlay.

I don't really think its the cats plugin that is causing it, even in blender 2.81 where I have any plugins or custom settings it still crashes, while in 2.8 it doesn't. The mesh itself has a problem somewhere, If I remesh it or decimate until a certain threshold it stops crashing.

I managed to reduce the size of the file to 161mb, tho I don't think I can reduce it even further.

Extra notes: in sculpt mode it doesn't crash when going to wireframe mode.

The problem with this bug is that I don't really think its easily reproducible, I'm pretty sure I already got this many times, whenever I finish a sculpt and start the retopo, when I go to wireframe it crashes. I tried remake what I did to the model before: I used boolean,multiresolution, regular subdivision, increased the poly count to 8 million, tried to use dyntopo but any of those seems to make a difference. The problem seems to be directly related to the wireframe, it also crashes if I activate the wireframe in the solid mode overlay. I don't really think its the cats plugin that is causing it, even in blender 2.81 where I have any plugins or custom settings it still crashes, while in 2.8 it doesn't. The mesh itself has a problem somewhere, If I remesh it or decimate until a certain threshold it stops crashing. I managed to reduce the size of the file to 161mb, tho I don't think I can reduce it even further. Extra notes: in sculpt mode it doesn't crash when going to wireframe mode.

Germano Cavalcante commented

2021-05-03 20:32:03 +02:00

For bug reports 100 MB is the maximum size indicated. But if it is the only way to reproduce the bug, we can make an exception.
Large file crashes are often due to RAM limitations (or GPU VRAM).
This makes it difficult for developers to investigate (since they need access to the hardware).
And while we want to improve Blender to handle such cases memory gracefully, this is not currently considered a bug.

Note: The crash log points to a problem in python so it is quite possible that some addon is triggering the conflict that leads to the crash.

For bug reports 100 MB is the maximum size indicated. But if it is the only way to reproduce the bug, we can make an exception. Large file crashes are often due to RAM limitations (or GPU VRAM). This makes it difficult for developers to investigate (since they need access to the hardware). And while we want to improve Blender to handle such cases memory gracefully, this is not currently considered a bug. Note: The crash log points to a problem in python so it is quite possible that some addon is triggering the conflict that leads to the crash.

Diogo Valadares Reis dos Santos commented

2021-05-03 20:53:55 +02:00

I don't really think its a memory issue, since heavier files don't crash in my computer, and again, there are situations where it doesn't crash, for example when you just open the file and don't move the camera, going directly to wireframe mode.

I looked the crash file again and it seems that it is from a previous crash, from day 4/30, so I don't think its related to this last crash, so sorry for that.

I ran the debug log once again, now with factory settings enabled on startup to make sure it isn't any addon. The output debug file is simply blank for some reason.

blender_system_info.txt
blender_debug_output.txt
untitled.blend

open the file above
rotate it about 180degrees
activate wireframe

I don't really think its a memory issue, since heavier files don't crash in my computer, and again, there are situations where it doesn't crash, for example when you just open the file and don't move the camera, going directly to wireframe mode. I looked the crash file again and it seems that it is from a previous crash, from day 4/30, so I don't think its related to this last crash, so sorry for that. I ran the debug log once again, now with factory settings enabled on startup to make sure it isn't any addon. The output debug file is simply blank for some reason. [blender_system_info.txt](https://archive.blender.org/developer/F10051806/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F10051807/blender_debug_output.txt) [untitled.blend](https://archive.blender.org/developer/F10051747/untitled.blend) - open the file above - rotate it about 180degrees - activate wireframe

Philipp Oeser commented

2021-05-28 08:18:53 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Philipp Oeser commented

2021-09-24 13:00:08 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-09-24 13:00:08 +02:00

Cannot reproduce here

**System Information**
Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits
Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.31
version: 3.0.0 Alpha, branch: master, commit date: 2021-09-24 09:24, hash: `rBd8a5b768f076`

Cannot reproduce here ``` **System Information** Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.31 version: 3.0.0 Alpha, branch: master, commit date: 2021-09-24 09:24, hash: `rBd8a5b768f076` ```

Philipp Oeser commented

2021-09-24 13:03:47 +02:00

Added subscribers: @JacquesLucke, @Jeroen-Bakker, @ThomasDinges

Philipp Oeser commented

2021-09-24 13:03:47 +02:00

@ThomasDinges , @Jeroen-Bakker, @JacquesLucke : you have similar GPUs, is this something you can reproduce?

Jacques Lucke commented

2021-09-24 13:30:32 +02:00

Switching to wireframe works without problems for me.
Maybe I'm doing something wrong. The instructions are not entirely clear. "Rotate it about 180 degrees", what is "it"? Is it important which method is used to activate wireframes?

Switching to wireframe works without problems for me. Maybe I'm doing something wrong. The instructions are not entirely clear. "Rotate it about 180 degrees", what is "it"? Is it important which method is used to activate wireframes?

Philipp Oeser commented

2021-09-24 13:54:22 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2021-09-24 13:54:22 +02:00

Thx testing.
The video shows it is just about rotating the view and it uses the pie shading menu to change between solid and wireframe.

In any case, before we get stuck here [since no-one can reproduce] I would kindly ask to try upgrading GPU drivers one more time:
You are using : Context 21.2.3 27.20.14535.3005
There seem to benwer available on https://www.amd.com/en/support/graphics/amd-radeon-5700-series/amd-radeon-rx-5700-series/amd-radeon-rx-5700-xt
Radeon Software Adrenalin 21.9.2 Driver Version 21.30.17.05 for Windows® 10 (Windows Driver Store Version 30.0.13017.5006).
Radeon Software Adrenalin 21.8.2 Driver Version 21.20.25.01 for Windows® 10 (Windows Driver Store Version 27.20.22025.1006)

Thx testing. The video shows it is just about rotating the view and it uses the pie shading menu to change between solid and wireframe. In any case, before we get stuck here [since no-one can reproduce] I would kindly ask to try upgrading GPU drivers one more time: You are using : Context 21.2.3 27.20.14535.3005 There seem to benwer available on https://www.amd.com/en/support/graphics/amd-radeon-5700-series/amd-radeon-rx-5700-series/amd-radeon-rx-5700-xt Radeon Software Adrenalin 21.9.2 Driver Version 21.30.17.05 for Windows® 10 (Windows Driver Store Version 30.0.13017.5006). Radeon Software Adrenalin 21.8.2 Driver Version 21.20.25.01 for Windows® 10 (Windows Driver Store Version 27.20.22025.1006)

Diogo Valadares Reis dos Santos commented

2021-09-24 17:27:02 +02:00

yeah, it still does happen with the lastest AMD drivers, both 21.9.2 and 21.8.2 in blender 2.9 and 3.0 with default settings.

Also It doesn't need to be activated via pie menu, even by just turning wireframe overlay here crashes blender:

"Rotate it about 180 degrees", what is "it"? Is it important which method is used to activate wireframes?

Sometimes moving the camera just a little bit didn't trigger the crash, It was just to make sure you rotate the camera enough to trigger the crash.

yeah, it still does happen with the lastest AMD drivers, both 21.9.2 and 21.8.2 in blender 2.9 and 3.0 with default settings. Also It doesn't need to be activated via pie menu, even by just turning wireframe overlay here crashes blender: ![image.png](https://archive.blender.org/developer/F10572264/image.png) >> "Rotate it about 180 degrees", what is "it"? Is it important which method is used to activate wireframes? Sometimes moving the camera just a little bit didn't trigger the crash, It was just to make sure you rotate the camera enough to trigger the crash.

Philipp Oeser commented

2021-09-24 18:18:08 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Diogo Valadares Reis dos Santos commented

2021-09-27 00:42:31 +02:00

So, I was sculpting a model and I just found one possible cause of the bug. The model is fine, no crashs in wiremode until I use symmetrize in sculpt mode.
After that, the wireframe mode starts causing crashes exacly the same way the model on this report is doing.

I tried to see if I could find a temporary fix for this problem and it seems like running the 3D print addon clean up(Make manifold) at least once solves it.

So, I was sculpting a model and I just found one possible cause of the bug. The model is fine, no crashs in wiremode until I use symmetrize in sculpt mode. After that, the wireframe mode starts causing crashes exacly the same way the model on this report is doing. I tried to see if I could find a temporary fix for this problem and it seems like running the 3D print addon clean up(Make manifold) at least once solves it.

Philipp Oeser commented

2022-02-21 09:22:32 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2022-02-21 09:22:32 +01:00

In #87970#1226174, @Diogo_Valadares wrote:
So, I was sculpting a model and I just found one possible cause of the bug. The model is fine, no crashs in wiremode until I use symmetrize in sculpt mode.
After that, the wireframe mode starts causing crashes exacly the same way the model on this report is doing.

Could you share that model here, too (prior to symmetrizing?)
Reproduction steps would then be:

open the file
enter sculptmode
symmetrize
enter objectmode
rotate viewport about 180degrees
activate wireframe

right?

Also please test if this is still an issue in recent 3.1 / 3.2 builds from https://builder.blender.org/download/daily/ (terribly sorry this has been lying around for so long btw.)

> In #87970#1226174, @Diogo_Valadares wrote: > So, I was sculpting a model and I just found one possible cause of the bug. The model is fine, no crashs in wiremode until I use symmetrize in sculpt mode. > After that, the wireframe mode starts causing crashes exacly the same way the model on this report is doing. Could you share that model here, too (prior to symmetrizing?) Reproduction steps would then be: - open the file - enter sculptmode - symmetrize - enter objectmode - rotate viewport about 180degrees - activate wireframe right? Also please test if this is still an issue in recent 3.1 / 3.2 builds from https://builder.blender.org/download/daily/ (terribly sorry this has been lying around for so long btw.)

Diogo Valadares Reis dos Santos commented

2022-02-21 22:02:05 +01:00

I do not have the model that was crashing after the symmtry anymore. but the one that is contained in this thread still crashes in 3.2. If I manage to reproduce it again I will upload it.

I may ask, If I run it in a debug build would it be possible to find what is causing the problem?

I do not have the model that was crashing after the symmtry anymore. but the one that is contained in this thread still crashes in 3.2. If I manage to reproduce it again I will upload it. I may ask, If I run it in a debug build would it be possible to find what is causing the problem?

Philipp Oeser commented

2022-03-24 15:01:37 +01:00

In #87970#1311523, @Diogo_Valadares wrote:
I may ask, If I run it in a debug build would it be possible to find what is causing the problem?

If you attach a debugger, yes, that would probably tell you where exactly this crash occurs (since blender_debug_output.txt is empty and we apparently dont get blender.crash.txt)
Let us know if this is going anywhere, thx in advance.

> In #87970#1311523, @Diogo_Valadares wrote: > I may ask, If I run it in a debug build would it be possible to find what is causing the problem? If you attach a debugger, yes, that would probably tell you where exactly this crash occurs (since blender_debug_output.txt is empty and we apparently dont get blender.crash.txt) Let us know if this is going anywhere, thx in advance.

Philipp Oeser commented

2022-04-05 10:47:05 +02:00

Last poke (without reaction, report will be closed next week)

Diogo Valadares Reis dos Santos commented

2022-04-05 19:09:54 +02:00

sorry, I was having some problems with the debugging.

I tracked down what was causing the problem and it seems to be in "gl_vertex_buffer.cc" in line 97

with the exception being

Does this helps someway?

sorry, I was having some problems with the debugging. I tracked down what was causing the problem and it seems to be in "gl_vertex_buffer.cc" in line 97 ```97 memory_usage += vbo_size_; ``` with the exception being ```Generated exception in 0x00007FFC4BA58C07 (atio6axx.dll) in blender.exe: 0xC0000005: Access violation trying to read 0x0000000000000000. ``` ![image.png](https://archive.blender.org/developer/F12976393/image.png) Does this helps someway?

Philipp Oeser commented

2022-04-05 20:09:15 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Philipp Oeser commented

2022-04-06 09:59:12 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Philipp Oeser commented

2022-04-06 09:59:12 +02:00

Added subscriber: @fclem

Philipp Oeser commented

2022-04-06 09:59:12 +02:00

In #87970#1336091, @Diogo_Valadares wrote:
sorry, I was having some problems with the debugging.

I tracked down what was causing the problem and it seems to be in "gl_vertex_buffer.cc" in line 97
with the exception being
Does this helps someway?

@fclem , @Jeroen-Bakker : does this ring a bell?

> In #87970#1336091, @Diogo_Valadares wrote: > sorry, I was having some problems with the debugging. > > I tracked down what was causing the problem and it seems to be in "gl_vertex_buffer.cc" in line 97 > ```97 memory_usage += vbo_size_; > ``` > > with the exception being > ```Generated exception in 0x00007FFC4BA58C07 (atio6axx.dll) in blender.exe: 0xC0000005: Access violation trying to read 0x0000000000000000. > ``` > ![image.png](https://archive.blender.org/developer/F12976393/image.png) > > Does this helps someway? @fclem , @Jeroen-Bakker : does this ring a bell?

Clément Foucault commented

2022-04-06 10:31:44 +02:00

The callstack seems to indicate a crash inside the AMD driver. The error line seems off as this is not a GL function call.

Philipp Oeser commented

2022-04-12 20:44:01 +02:00

So how would be classify this? Any chance to progress here? I am out of ideas

Moritz commented

2022-12-03 22:34:22 +01:00

Added subscriber: @Lucott

Moritz commented

2022-12-03 22:34:22 +01:00

Today I wanted to report this bug but I found that this thread already existed.
I have 2 different machines with 2 completly different hardware systems and I experienced this bug on both machines.

Blender 3.4 Release Candidate

System 1: 128gb RAM + RTX 4090
System 2: 64gb RAM + RTX 2070 Super

When I load blender for the first time and switch from object mode to wireframe via Pie Menu it crashes instantly. Subdivision surface Modifier seems to increase the frequency of this problem.
What is the current Progress on this bug?

Today I wanted to report this bug but I found that this thread already existed. I have 2 different machines with 2 completly different hardware systems and I experienced this bug on both machines. Blender 3.4 Release Candidate System 1: 128gb RAM + RTX 4090 System 2: 64gb RAM + RTX 2070 Super When I load blender for the first time and switch from object mode to wireframe via Pie Menu it crashes instantly. Subdivision surface Modifier seems to increase the frequency of this problem. What is the current Progress on this bug?

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

crash when changing viewport shading to wireframe mode #87970