Import or export of GLB crashes Blender #83685
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#83685
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: Ubuntu Groovy Gorilla
Graphics card: Intel Corporation Iris Plus Graphics 655 (rev 01)
Blender Version
Broken: 2.91.0 2020-11-25 (snap package)
Worked:
Short description of error
Either importing or exporting a GLB file, even starting from the simplest possible .blend file (empty because I deleted the starting cube, and freshly opened) causes a crash.
Exact steps for others to reproduce the error
I am attaching a GLB. Click File >> Import >> GLB and select it. Blender crashes.
I am attaching a Wavefront OBJ file. Import that, then File >> Export >> GLB and crash. shinypointer.obj
shinybluepointer.glb
Added subscriber: @carlf
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Needs User Info'
I can't reproduce a crash. Could you please run Blender with debug flags and attach the log file. Please also upload the crash log that should be found in
/tmp
.Thanks for looking into this. I attach the output file defined above.
No crash file seems to have been generated. This command finds nothing:
find / -name "crash" | grep blend | less
I can run Blender inside a debugger if desired.
Again, thank you.
blender_debug_output.txt
Could you try this again with a portable Blender version ?
@carlf Could you please try to repeat the test with the non-snap version of Blender?
Works fine in the older version of Blender supplied with this version of Ubuntu. I downloaded the snap version specifically because I thought I needed the latest version, but actually I was just confused by the remarkably complex and unintuitive (sorry) interface of Blender.
If it would be useful to you, I could try to install (would I need to compile?) the bleeding-edge version to test for you.
@carlf You can simply download and extract the portable version mentioned in my comment above. No installation or compilation required. Although building it yourself using a debugger would certainly give you a stack trace if the crash happens within Blender.
Added subscriber: @ry167
I am getting this issue as well. I tried downloading the standalone version and the issue persisted.
I tried removing all user settings (
rm -rf ~/.config/blender
) and starting the standalone one only. The Import GLB dialog opens but crashes once you confirm a file to import.The Export item crashes Blender before opening the file dialog.
I checked in v2.92 alpha and v2.90.1 and it seems to happen in all of them.
Logs contents was the exact same as @carlf
Operating system: Pop!_OS 20.10 (based on Ubuntu 20.10 Groovy Gorilla)
GPU: Mesa Intel® Xe Graphics (TGL GT2)
Happy to help where I can with debugging
Sorry about the delay. I just tested the current (production, non-alpha) version from blender.org and it crashes on attempts to either import or export GLB. As before, OS is Groovy Gorilla.
As I say, I can install and run a debugger if that would help.
@carlf That would be very helpful as I can't reproduce this problem on Ubuntu 20.04.1.
Just now with a brand-new download of 2.91.0. Here's what gdb says:
"locate raise.c" reports several copies of "fix_raise.cpython-nn" but no actual copies of raise.c.
I installed gnulib, which supplies raise.c, but Blender still crashes on GLB import. Since gnulib installed raise.c in /usr/share/gnulib/lib/ and (as shown above) Blender wants it to be in ../sysdeps/unix/sysv/linux/, I created ~/Downloads/unix/sysv/linux (I have the downloaded blender executable in ~//Downloads/blender-2.91.0-linux64) and softlinked raise.c there.
Now gdb's trace ends with:
I hope that's helpful.
Exporting to GLB appears to work fine when running from a script without the UI, as in
blender -b -P something.py
but fails when trying from within the UI scripting interface with something likebpy.ops.export_scene.gltf(filepath='~/test.glb')
.I also get the same result in
gdb
.Entering
bt
into GDB I get:I believe the error is in Python code which I can't see any simple debugging instructions for.
Perhaps this is something that should also be posted to https://github.com/KhronosGroup/glTF-Blender-IO/ ? Though I can't tell if its Blender Python or Add On Python that is having the issue...
I hope that helps!
Added subscriber: @JulienDuroure
Could you please try to start Blender with the
--factory-startup
flag and repeat the attempt to export the file? Then also do the same with the lastest daily build of Blender 2.92. . This is to rule out issues caused by other Python add-ons.@JulienDuroure This could be something for you to look at.
Hello,
Currently, I can't reproduce neither (tested on stable 2.91 or today's build) on linux Mint
But :
@rjg, Both with 2.91 and the 2.92 alpha, same crash with --factory-startup. Did not try in the debugger.
This might be unrelated to glTF and rather an issue with the snap package. A similar crash was reported with the A.N.T.Landscape add-on in #84752.As mentioned, though, the identical thing happens with several non-snap versions.
Right, ignore the previous comment then. Phabricator hides old comments and I missed that we already tested this.
We have a identified a potential cause in #84752. Given that the provided stack trace here also goes through ctypes and has similar symptoms, I believe this is the same problem. This might be caused by the function
CFUNCTYPE(c_int)(lambda: None)
called by_reset_cache
in2.9x/python/lib/python3.7/ctypes/__init__.py
which has been removed in newer versions of Python.Could you please create a copy of the
__init__.py
file and rename it to have a copy of the original. Then edit the__init__.py
and remove the line from the file, then check if the crash still occurs? It should be line 273. Afterwards you can remove the edited file rename the copy back to__init__.py
.@rjg, you are a very smart person. That worked in 2.92.0-057a8afb879c-linux64. Thank you.
I haven't been involved in software development for a while, but shouldn't a problem like "an invalid Python function call" produce a useful error message, not just die? (Not criticizing you, wondering about Python 3.7.)
Thanks, really.
I'm not sure where the python file update needed to go, so for now based on the initial report in #84752 I have uninstalled Blender via Snap and reinstalled it via Flatpak which has allowed me to continue working
This is a duplicate of #84752
Closed as duplicate of #84752