Selecting Materials after creating a new file throws EXCEPTION_ACCESS_VIOLATION #63698
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#63698
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.17763 64 Bits
Graphics card: GeForce GTX 260M/PCIe/SSE2 NVIDIA Corporation 3.3.0
Blender Version
Broken: version: 2.80 (sub 57), branch: blender2.7, commit date: 2019-04-17 19:26, hash:
b46245470f
Worked: version: 2.80 (sub 55), branch: blender2.7, commit date: 2019-04-09 18:12, hash:
009dbc2bc9
Short description of error
This is kind of weird, but I'll try to be concise as possible. If I open Blender with the default startup file and select materials, it crashes. If I open it with the default start up file, select Cycles, then back to Eevee (instantly), then materials, it also crashes. However if I change from Eevee to Cycles, click the materials tab, then change back to Eevee, then select materials again, it doesn't crash.
After all that, hitting Ctrl+N and creating a new general file, and selecting materials then causes the crash to happen again.
Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]
Also, I was digging through and found the debug cmd scripts. I used the blender_factory_startup one, and have attached the text files.blender_system_info.txt
blender_debug_output.txt
Added subscriber: @Yu-sion
#63760 was marked as duplicate of this issue
#63711 was marked as duplicate of this issue
#63704 was marked as duplicate of this issue
Crash on selecting Materials after creating a new fileto Selecting Materials after creating a new file throws EXCEPTION_ACCESS_VIOLATIONContinued to play it a bit and found that hitting Z and selecting Rendered or LookDev display modes also crashes the program. I replicated this using the same blender_factory_startup.cmd script, and all 3 seem to generate the same output in the blender_debug_output.txt file. I know I had no problems with the Rendered display mode in the previous build mentioned above.
P.S. First time submitting a bug report to you guys, please let me know if I can include anything else to help you resolve this. :)
Added subscribers: @LazyDodo, @brecht, @ZedDB
Unsure if I can confirm this or not. I do not get any crashes, but I do get ASAN errors when opening up the materials tab:
Also getting these two on startup:
@LazyDodo @brecht are these harmless errors or will these lead to crashes?
@Yu-sion are you using the latest nvidia drivers for your card?
These kinds of errors are not harmless I think. They might be the same as #63046 (Crashing loading .blend file with missing paint tool slots).
Added subscriber: @Adamsuper
@ZedDB, yes, I am.
GEFORCE 342.01 DRIVER
Version: 342.01 WHQL
Release Date: 2016.12.14
Edit to add: I still have a copy of the previous working version as mentioned above (version: 2.80 (sub 55), branch: blender2.7, commit date: 2019-04-09 18:12, hash:
009dbc2bc9
) still on my harddrive and I can still use it without any of these errors. Something has changed between then that is causing this crash for me.@Adamsuper are you using the latest drivers for your card?
@Yu-sion are you able to build blender by yourself by any chance? If so you could try to git bisect search and find the commit that broke this for you.
@ZedDB Well, I do some programming myself and I found the step-by-step guide on Building Blender on the wiki, fairly confident I can do it. My knowledge on git however is pretty basic, not sure about my ability to do a bisect search.
Added subscriber: @AlvandroX
Seems like a lot of people has issues now, so I'll raise the priority.
@Yu-sion It is not that hard: https://git-scm.com/book/en/v2/Git-Tools-Debugging-with-Git
Basically you go the blender source code directory type
git bisect start
.Then you can do
git bisect good <commit hash of blender build that works>
andgit bisect bad
orgit bisect bad <commit hash of bad build>
.After that you build blender and run it. If the current build works without any issues you type
git bisect good
andbad
if it doesn't work.You then rebuild blender (as bisect switches commits for you) until you narrow down the bad commit.
@ZedDB Oh yeah, pretty sure I watched a video on that. Downloading the libraries now, and I have some stuff I need to do this morning, but I'll give it a shot later today or sometime tomorrow and report back. :)
Great! :)
Added subscriber: @WeslleydaSilvaFernandes
This comment was removed by @Yu-sion
@ZedDB I just wanted to let you know I haven't forgotten, but as I do C# programming I don't have the C++ workload downloaded for MSVS 2017, and my connection isn't exactly the fastest. But I will try to get it done over the weekend.
Also, sorry, I didn't mean to add Weslley, I just wanted to say I have/had (almost) the same problem he reported here , only mine doesn't crash it just hangs and stops responding. So I might try to look into that as well.
Added subscriber: @Gvgeo-1
@Gvgeo-1, @ZedDB,
Can confirm this (#63698) and #63760 are related (or were at least broken in the same commit I guess would be better wording). As promised, I just got done doing a bisect search, and every time that clicking Materials caused a crash, selecting either Rendered or LookDev display modes would also cause a crash. They also both give me the exact same error output from the debug cmd scripts.
Here's the bisect log and result.
And since I have limited experience with C++ I leave the rest to you guys, haha. I hope this helps though. :)
P.S. I'm probably never doing that again. Unless I'm doing something wrong, those build times are crazy on an old 2.53GHz dual core. :(
This issue was referenced by
c8fc23fdbe
Changed status from 'Open' to: 'Resolved'
Added subscriber: @vidhiyasagar
Thanks for tracking down the commit. I committed a fix, but I was not able to reproduce myself so please test if it actually worked in the next build.
Thank you, @brecht, commit
c8fc23fdbe
has fixed the reported issues with the materials tab along with the lookdev and rendered display modes..