Crash when opening file #79533

Closed
opened 2020-08-04 23:22:33 +02:00 by Aeron Farax · 33 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92

Blender Version
Broken: version: 2.90.0 Beta, branch: master, commit date: 2020-08-04 18:05, hash: 97be726f93

Short description of error
Blender crashes when opening file directly

Exact steps for others to reproduce the error
#79533.blend

Open file by dragging it on to blender.exe file. Or run command blender #79533.blend in console

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92 **Blender Version** Broken: version: 2.90.0 Beta, branch: master, commit date: 2020-08-04 18:05, hash: `97be726f93` **Short description of error** Blender crashes when opening file directly **Exact steps for others to reproduce the error** [#79533.blend](https://archive.blender.org/developer/F8791865/T79533.blend) Open file by dragging it on to blender.exe file. Or run command `blender #79533.blend` in console
Author

Added subscriber: @forcef

Added subscriber: @forcef

#77910 was marked as duplicate of this issue

#77910 was marked as duplicate of this issue

Added subscriber: @iss

Added subscriber: @iss

What are steps to reproduce? Just keep switching from wireframe to rendered shading?

When crash happens, crash file should be mentioned in the end of blender_debug_output.txt file. can you upload that file as well?

What are steps to reproduce? Just keep switching from wireframe to rendered shading? When crash happens, crash file should be mentioned in the end of `blender_debug_output.txt` file. can you upload that file as well?
Author

That .text is included in .zip that was after crash, i used especially blender_debug_log.cmd to launch blender before. Logs from today and when video goes dark = crash but sometimes you have to switch much much more to even get crash if not at all. Maybe this is unresolveable dont know or just GPU hiccup.

debug_logs.zip
2020-08-05 11-35-05.mp4

That .text is included in .zip that was after crash, i used especially blender_debug_log.cmd to launch blender before. Logs from today and when video goes dark = crash but sometimes you have to switch much much more to even get crash if not at all. Maybe this is unresolveable dont know or just GPU hiccup. [debug_logs.zip](https://archive.blender.org/developer/F8747753/debug_logs.zip) [2020-08-05 11-35-05.mp4](https://archive.blender.org/developer/F8747754/2020-08-05_11-35-05.mp4)
Author

Little update, digged up old Udemy pyramid from last year and that can trigger crash too when switching view modes.
udemy_pyramid.crash.zip
udemy_pyramid.zip

Little update, digged up old Udemy pyramid from last year and that can trigger crash too when switching view modes. [udemy_pyramid.crash.zip](https://archive.blender.org/developer/F8748228/udemy_pyramid.crash.zip) [udemy_pyramid.zip](https://archive.blender.org/developer/F8748231/udemy_pyramid.zip)
Author

Updating crash logs from 4f59e4bddc and crashes still same. Tested 2.83.4 and no problems at all.

debug_logs.zip
blender_debug_gpu_glitchworkaround.zip

Updating crash logs from 4f59e4bddcb0 and crashes still same. Tested 2.83.4 and no problems at all. [debug_logs.zip](https://archive.blender.org/developer/F8756748/debug_logs.zip) [blender_debug_gpu_glitchworkaround.zip](https://archive.blender.org/developer/F8756749/blender_debug_gpu_glitchworkaround.zip)
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

This looks like #77910 (Sometimes the Viewport is damaged.) could be the same / related?

This looks like #77910 (Sometimes the Viewport is damaged.) could be the same / related?
Author

In #79533#994329, @lichtwerk wrote:
This looks like #77910 (Sometimes the Viewport is damaged.) could be the same / related?

Do not know, in some angles reminds that too but for me sometimes mesh faces could reach infinite distance like on my picture. I really do not know and i give info as much blender debug launchers give. Last test i made was Aug 7 and those bugs prevented me testing further and now i use 2.83.4. I too started from clean settings like i always do if moving major versions and set up my personal settings again.

> In #79533#994329, @lichtwerk wrote: > This looks like #77910 (Sometimes the Viewport is damaged.) could be the same / related? Do not know, in some angles reminds that too but for me sometimes mesh faces could reach infinite distance like on my picture. I really do not know and i give info as much blender debug launchers give. Last test i made was Aug 7 and those bugs prevented me testing further and now i use 2.83.4. I too started from clean settings like i always do if moving major versions and set up my personal settings again.
Author

Drag and dropping .blend to blender.exe causes instant crash sometimes, even if .blend is saved fresh from 2.9 c5519d4b6f. User prefs was set up fresh again too. Strange is that only glitch workaround gives more info than others but stops in middle as you see in log. I am no programmer.

Very weird is that when launching with blender_debug_gpu.cmd then it is very hard to get crash, weird or it is really a coincidence.

blender_debug_gpu_glitchworkaround.zip

Drag and dropping .blend to blender.exe causes instant crash sometimes, even if .blend is saved fresh from 2.9 c5519d4b6f7f. User prefs was set up fresh again too. Strange is that only glitch workaround gives more info than others but stops in middle as you see in log. I am no programmer. Very weird is that when launching with blender_debug_gpu.cmd then it is very hard to get crash, weird or it is really a coincidence. [blender_debug_gpu_glitchworkaround.zip](https://archive.blender.org/developer/F8780028/blender_debug_gpu_glitchworkaround.zip)
Author

I am not sure but could this be connected somehow when opening files and something happens in time when opening? Appending objects then all works fine.

I am not sure but could this be connected somehow when opening files and something happens in time when opening? Appending objects then all works fine.

Added subscriber: @YAFU

Added subscriber: @YAFU

This looks like the problem that many of us are randomly having:
https://developer.blender.org/T77910

Edit:
Oh, Philipp already mentioned it.

This looks like the problem that many of us are randomly having: https://developer.blender.org/T77910 Edit: Oh, Philipp already mentioned it.
Richard Antalik changed title from Crash and autosaved corruptions/defects to Crash when opening file 2020-08-19 00:08:53 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

Added subscriber: @fclem

Added subscriber: @fclem

I was able to reproduce crash when running command blender.exe #79533.blend

 	atio6axx.dll!00007ffaa7f1b1e7()	Unknown
>	blender.exe!GPU_framebuffer_bind(GPUFrameBuffer * fb) Line 527	C++

 	blender.exe!DRW_draw_render_loop_ex(Depsgraph * depsgraph, RenderEngineType * engine_type, ARegion * region, View3D * v3d, GPUViewport * viewport, const bContext * evil_C) Line 1510	C
 	blender.exe!DRW_draw_view(const bContext * C) Line 1404	C
 	[Inline Frame] blender.exe!view3d_draw_view(const bContext *) Line 1598	C
 	blender.exe!view3d_main_region_draw(const bContext * C, ARegion * region) Line 1622	C
 	blender.exe!ED_region_do_draw(bContext * C, ARegion * region) Line 543	C
 	blender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 697	C
 	blender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 825	C
 	blender.exe!wm_draw_update(bContext * C) Line 1028	C
 	blender.exe!WM_main(bContext * C) Line 483	C
 	blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 548	C
 	[External Code]	

This does not look to be the same issue as with CHEST.blend in #77910. but that file may have different issues. File udemy_pyramid.blend opened without problems.
Perhaps these glitches occur only with somehow broken files?

In any case this stack trace looks like it may be closer to the actual problem, so I will confirm this.

CC @fclem

I was able to reproduce crash when running command `blender.exe #79533.blend` ``` atio6axx.dll!00007ffaa7f1b1e7() Unknown > blender.exe!GPU_framebuffer_bind(GPUFrameBuffer * fb) Line 527 C++ blender.exe!DRW_draw_render_loop_ex(Depsgraph * depsgraph, RenderEngineType * engine_type, ARegion * region, View3D * v3d, GPUViewport * viewport, const bContext * evil_C) Line 1510 C blender.exe!DRW_draw_view(const bContext * C) Line 1404 C [Inline Frame] blender.exe!view3d_draw_view(const bContext *) Line 1598 C blender.exe!view3d_main_region_draw(const bContext * C, ARegion * region) Line 1622 C blender.exe!ED_region_do_draw(bContext * C, ARegion * region) Line 543 C blender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 697 C blender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 825 C blender.exe!wm_draw_update(bContext * C) Line 1028 C blender.exe!WM_main(bContext * C) Line 483 C blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 548 C [External Code] ``` This does not look to be the same issue as with `CHEST.blend` in #77910. but that file may have different issues. File `udemy_pyramid.blend` opened without problems. Perhaps these glitches occur only with somehow broken files? In any case this stack trace looks like it may be closer to the actual problem, so I will confirm this. CC @fclem
Author

I think those were not broken as i saved even fresh files from latest 2.9 build and still sometimes crashes occurred or those infinite reaching planes. If i have way to get better info i would give but now i do not know what to give anymore. 2.83.4 do not have any of that if compared to 2.9 latest builds.

Just in case i post my config if it gives something useful at all(it is made fresh on e157573fab build, not just moved from older one)
config.zip

No error on my drive as i tested even with other fresh ssd drive.

Edit 20.08.2020: Friend confirmed same thing, about 30-40% happens when opening file and there will be crashes.

I think those were not broken as i saved even fresh files from latest 2.9 build and still sometimes crashes occurred or those infinite reaching planes. If i have way to get better info i would give but now i do not know what to give anymore. 2.83.4 do not have any of that if compared to 2.9 latest builds. Just in case i post my config if it gives something useful at all(it is made fresh on e157573fab2a build, not just moved from older one) [config.zip](https://archive.blender.org/developer/F8792259/config.zip) No error on my drive as i tested even with other fresh ssd drive. Edit 20.08.2020: Friend confirmed same thing, about 30-40% happens when opening file and there will be crashes.
Author

Still same as with build ebf10b72b0, this time crash is again when switching modes and when i hit shading mode then crash came.

debug_logs.zip

Again, i set up my settings from fresh and did not port my previous to current build. Just to be sure.

Still same as with build ebf10b72b05f, this time crash is again when switching modes and when i hit shading mode then crash came. [debug_logs.zip](https://archive.blender.org/developer/F8808097/debug_logs.zip) Again, i set up my settings from fresh and did not port my previous to current build. Just to be sure.

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker

Ok I was able to reproduce on Windows + NVidia but only on release mode.

It seems to me that the issue is threading related (cc @Jeroen-Bakker) as it vanished as soon as I'm using -t 1 parameter. I could not get any debug callstack trace.

One thing that got me thinking it was threading related, is that during one of my test, the biggest box got smooth shaded even if it is not in reallity.

So it might be related to something like #79038.

Ok I was able to reproduce on Windows + NVidia but only on release mode. It seems to me that the issue is threading related (cc @Jeroen-Bakker) as it vanished as soon as I'm using `-t 1` parameter. I could not get any debug callstack trace. One thing that got me thinking it was threading related, is that during one of my test, the biggest box got smooth shaded even if it is not in reallity. So it might be related to something like #79038.
Member

@fclem to get the stack trace you can always comment out drw_mesh_batch_cache_check_available(task_graph, me); in draw_cache_impl_mesh.c

@fclem to get the stack trace you can always comment out `drw_mesh_batch_cache_check_available(task_graph, me);` in `draw_cache_impl_mesh.c`
Author

No idea about that, but i really hope that 2.90 final do not include this anomaly as i am quick runner with new versions because features will get better and usability becomes more and more comfortable with every new release. Somehow something is changed that 2.83.4 is solid as rock but 2.90 has some weird corruptions when opening, sometimes crash, sometimes models reach to infinite and sometimes are with borked shading in workbench like in first post images or switching shading mode causes a crash.

Config again if that matters at all.
config.zip

EDIT: some more test, this time crash was when entered edit mode and boom, crash.
debug_logs.zip

And i opened my old Udemy chess(just for another sample) about 17 times until i got heavy anomalies.
2.90 anomaly.png
second opening
2.90 anomaly 2.png
udemy_lp_chess.zip

No idea about that, but i really hope that 2.90 final do not include this anomaly as i am quick runner with new versions because features will get better and usability becomes more and more comfortable with every new release. Somehow something is changed that 2.83.4 is solid as rock but 2.90 has some weird corruptions when opening, sometimes crash, sometimes models reach to infinite and sometimes are with borked shading in workbench like in first post images or switching shading mode causes a crash. Config again if that matters at all. [config.zip](https://archive.blender.org/developer/F8808323/config.zip) EDIT: some more test, this time crash was when entered edit mode and boom, crash. [debug_logs.zip](https://archive.blender.org/developer/F8809142/debug_logs.zip) And i opened my old Udemy chess(just for another sample) about 17 times until i got heavy anomalies. ![2.90 anomaly.png](https://archive.blender.org/developer/F8809147/2.90_anomaly.png) second opening ![2.90 anomaly 2.png](https://archive.blender.org/developer/F8809149/2.90_anomaly_2.png) [udemy_lp_chess.zip](https://archive.blender.org/developer/F8809151/udemy_lp_chess.zip)

This issue was referenced by 141a8ff6b3

This issue was referenced by 141a8ff6b3b1170d5551ef08895f1b7fac145235
Jeroen Bakker self-assigned this 2020-08-25 08:22:43 +02:00
Member

Workaround added for 2.90. I keep this ticket open to research a better solution or to make the workaround permanent.

Workaround added for 2.90. I keep this ticket open to research a better solution or to make the workaround permanent.
Author

Definitely i test this when builder builds new build to see if it helped.

Definitely i test this when builder builds new build to see if it helped.

This issue was referenced by 263cf2ea94

This issue was referenced by 263cf2ea945ac1224023f92a9767111956ecca24
Author

It really seems that 21cb6f09ff really has fixed this horrible menace bug, i opened file and rapidly changed shadinga and ZERO crash. Little bug can cause so many errors and anomalies. Glad it is over. Thank you developers for detecting this and finding a cause.

I could not reproduce any of those issues anymore. I opened different files about 40-60x and all fine in every way. Please decide what you do with this report, close it or?

EDIT: 26.08.2020 18:35: Update note, used today lot of times and still very solid and zero anomalies and crashes.

EDIT: 28.08.2020 13.05: Still using latest 2.90 build and solid as rock. Actually would be really interested what was that if it is possible to describe to non-programmer generalist? Really this fixed that bug?

BLI_task_graph_work_and_wait(task_graph); ? Makes some threading wait until finishes? if i read it correctly.

It really seems that 21cb6f09ffa8 really has fixed this horrible menace bug, i opened file and rapidly changed shadinga and ZERO crash. Little bug can cause so many errors and anomalies. Glad it is over. Thank you developers for detecting this and finding a cause. I could not reproduce any of those issues anymore. I opened different files about 40-60x and all fine in every way. Please decide what you do with this report, close it or? EDIT: 26.08.2020 18:35: Update note, used today lot of times and still very solid and zero anomalies and crashes. EDIT: 28.08.2020 13.05: Still using latest 2.90 build and solid as rock. Actually would be really interested what was that if it is possible to describe to non-programmer generalist? Really this fixed that bug? BLI_task_graph_work_and_wait(task_graph); ? Makes some threading wait until finishes? if i read it correctly.
Contributor

Added subscriber: @Raimund58

Added subscriber: @Raimund58
Added subscribers: @ditos, @Udjanii, @matteolegna-2, @Mainman002, @Yaroslav-7, @ideasman42, @dfelinto, @mont29, @ZedDB, @Pasang, @DaveStromberger, @RedMser, @Thane5, @Jewls, @sharaths21312, @MichelAbassi, @MarcinTwarowski, @renderluz-2

Removed subscriber: @Yaroslav-7

Removed subscriber: @Yaroslav-7
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Member

We promoted the current work-around to a proper fix.

We promoted the current work-around to a proper fix.
Thomas Dinges added this to the 2.91 milestone 2023-02-08 16:21:41 +01:00
Sign in to join this conversation.
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
9 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#79533
No description provided.