Crash on toggle x-ray mode #87915
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#87915
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
8c73f44a01
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
and crash..
Visualizer Linear.blend
Added subscriber: @MuiscAMG
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Needs User Info'
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
Added subscriber: @PratikPB2123
Neither I can reproduce the crash. Blender Version: 3.0.0 alpha, Hash:
8e0995d006
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.
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..blender_debug_output.txt
and blender_system_info.txt
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.
Changed status from 'Needs User Info' to: 'Needs Triage'
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
@MuiscAMG , 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..
Changed status from 'Needs Triage' to: 'Resolved'
@MuiscAMG , thanks for checking.
Closing the task but feel free to reopen or submit a new report if problem reappears :)