EXCEPTION_ACCESS_VIOLATION on file opening #87151
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#87151
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: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89
Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash:
02948a2cab
Worked: version: 2.93.0 Alpha, branch: master, commit date: 2021-04-01 15:32, hash:
76cdcc2bca
Short description of error
I tried to open up a file with heavy geometry nodes (from someone else) but it immediately crashes.
Exact steps for others to reproduce the error
Customizable Screws.blend This is the file
Added subscriber: @Phonix-64
Added subscriber: @filedescriptor
Changed status from 'Needs Triage' to: 'Confirmed'
I can confirm the crash in 2.92.0. Not sure if we can call this a bug. But imo this shouldn't crash even if the file was saved in a never (Alpha) version.
Added subscriber: @Andrew_Pluzhnikov
Reproduced.
Customizable Screws.crash.txt
Wikipedia claims that .blend files are forward and backward compatible (with some exceptions).
(I can't find "official" statement on the blender side.)
Here we have a case of clear backward incompatibility between 2.93 and 2.92 versions.
I thinkwe can call that a bug.
Added subscribers: @dfelinto, @JacquesLucke
I found two reasons for why this not working:
9f68f5c1e
is the problem, but it could be any other new socket as well).Generally, the issue is that too often I did not think about the case when future files are opened in an older version. Often new features cannot be handled correctly in old versions of course, but we could do better than we do now.
I could come up with a fix for this that would need to be applied to 2.92, but I'm unsure if it is worth it (and if this is a somewhat common practice). @dfelinto, how likely is it that we do another release of 2.92 because of that? Doesn't seem likely to me. Increasing
BLENDER_FILE_MIN_VERSION
could be the solution as you suggested.Added subscriber: @mont29
Changed status from 'Confirmed' to: 'Archived'
Think it's time to archive that, we could only consider back-fixes in LTS cases anyway imho.