Page MenuHome

Crash on toggle x-ray mode
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon(TM) RX 560 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.12.1 27.20.14501.28009

Blender Version
Broken: version: 2.93.0 Beta, branch: master, commit date: 2021-04-29 09:42, hash: rB8c73f44a019c
Worked: (newest version of Blender that worked as expected)

Short description of error
When toggling x-ray mode, while in edit mode - crash

Exact steps for others to reproduce the error

  • In edit mode, Add a UV sphere
  • resize the sphere
  • Click in toggle x-ray mode

and crash..

Event Timeline

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Apr 30 2021, 5:21 PM
Germano Cavalcante (mano-wii) updated the task description. (Show Details)

I cannot reproduce this with either the latest stable or current development versions of Blender:

Please try the latest daily build: https://builder.blender.org/download/

Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

If the problem persists, please give us more clear instructions on how to reproduce it from scratch.

I build from the source code every couple of hours. Do you have an AMD graphics card? It's AMD related crash.

I tested on:
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001

Neither I can reproduce the crash. Blender Version: 3.0.0 alpha, Hash: 8e0995d0062


System Information
Operating system : Windows-10-10.0.18362-SP0 64 Bits
Graphics card : AMD Radeon(TM) 535 ATI Technologies .

Try the latest daily build and run blender_debug-gpu.cmd that is included in the download.
After Blender closes (due the crash), the logs will be in a text file which can be attached here.
Most likely it will contain more information about the error.

Herb Brown (MusicAMG) added a comment.EditedMay 7 2021, 2:45 PM

Well, almost more information.. the text file stopped being written to when it locked up. I ran 2 tests, enabling the the debug log each time. On the first run I did not purposely crash Blender with the bug. This was to give me information to look at in the logs (so I could make a comparison). The second run was with the crash and the only difference was it stopped writing after the last warning.

here are the two log files..


and

These logs show nothing that can really help :\
Try to load the Factory Settings (File → Defaults → Load Factory Settings).
Also double-check if the drivers are up to date.
To upgrade to the latest driver, see here for more information: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html

Factory settings have same result, and the drivers are up to date.

Only thing I can add is what I see when the crash happens, which is, one monitor goes white screen and the second monitor goes red screen. That behavior seems, to me, like GPU ram ran out of memory. Again, only happens when I turn on x-ray mode from the tool bar. noticed also this behavior present for me in version 2.92 of Blender.

So, either this bug is present for this particular card only, or, the card itself is bad.

Germano Cavalcante (mano-wii) changed the task status from Needs Information from User to Needs Triage.May 7 2021, 8:22 PM

If you could run a debug build with Visual Studio 2019 and enable ASAN, it may give you an idea. This is the info, it is somewhat new, but works as described.. https://docs.microsoft.com/en-us/cpp/sanitizers/asan?view=msvc-160

@Herb Brown (MusicAMG) , please add crash.txt file located at C:\Users\user_name\AppData\Local\Temp

Also see the attached link to upload the crash logs (https://docs.blender.org/manual/en/latest/troubleshooting/crash.html#windows)

For me, this has been resolved. Since the LTS release, the crash does not happen anymore..

@Herb Brown (MusicAMG) , thanks for checking.

Closing the task but feel free to reopen or submit a new report if problem reappears :)