Import or export of GLB crashes Blender #83685

New Issue

Carl Fink · 2020-12-11T23:50:04+01:00

Carl Fink commented

2020-12-11 23:50:04 +01:00

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

**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](https://archive.blender.org/developer/F9503448/shinypointer.obj) [shinybluepointer.glb](https://archive.blender.org/developer/F9503449/shinybluepointer.glb)

Carl Fink commented

2020-12-11 23:50:04 +01:00

Added subscriber: @carlf

Robert Guetzkow commented

2020-12-12 11:23:13 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-12-12 11:23:13 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Robert Guetzkow commented

2020-12-12 11:23:13 +01:00

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.

./blender --debug --debug-python --debug-io > ~/blender_debug_output.txt 2>&1

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`. ``` ./blender --debug --debug-python --debug-io > ~/blender_debug_output.txt 2>&1 ```

Carl Fink commented

2020-12-12 13:50:50 +01:00

In #83685#1073963, @rjg wrote:
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.
./blender --debug --debug-python --debug-io > ~/blender_debug_output.txt 2>&1

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

> In #83685#1073963, @rjg wrote: > 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`. > > ``` > ./blender --debug --debug-python --debug-io > ~/blender_debug_output.txt 2>&1 > ``` 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](https://archive.blender.org/developer/F9504595/blender_debug_output.txt)

Robert Guetzkow commented

2020-12-15 14:15:28 +01:00

Could you try this again with a portable Blender version ?

Download the blender-2.91.0-linux64.tar.xz
Extract it
Start Blender with the command line flags
Repeat the import test

Could you try this again with a portable [Blender version ](https://download.blender.org/release/Blender2.91/)? - Download the blender-2.91.0-linux64.tar.xz - Extract it - Start Blender with the command line flags - Repeat the import test

Robert Guetzkow commented

2020-12-23 16:55:37 +01:00

@carlf Could you please try to repeat the test with the non-snap version of Blender?

Carl Fink commented

2020-12-23 17:04:43 +01:00

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.

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.

Robert Guetzkow commented

2020-12-23 17:09:47 +01:00

@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.

Ryan commented

2020-12-30 12:06:48 +01:00

Added subscriber: @ry167

Ryan commented

2020-12-30 12:06:48 +01:00

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

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

Carl Fink commented

2020-12-31 03:45:12 +01:00

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.

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.

Robert Guetzkow commented

2020-12-31 15:26:40 +01:00

@carlf That would be very helpful as I can't reproduce this problem on Ubuntu 20.04.1.

Carl Fink commented

2021-01-01 22:22:25 +01:00

Just now with a brand-new download of 2.91.0. Here's what gdb says:

(gdb) run
Starting program: /home/carlf/Downloads/blender-2.91.0-linux64/blender 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff6dff640 (LWP 1296064)]
[New Thread 0x7ffff3bcf640 (LWP 1296065)]
[New Thread 0x7ffff33ce640 (LWP 1296066)]
[New Thread 0x7ffff2bcd640 (LWP 1296068)]
[New Thread 0x7ffff23cc640 (LWP 1296069)]
[New Thread 0x7ffff1bcb640 (LWP 1296070)]
[New Thread 0x7ffff13ca640 (LWP 1296071)]
[New Thread 0x7ffff0bc9640 (LWP 1296072)]
[New Thread 0x7ffff03c8640 (LWP 1296073)]
[Detaching after vfork from child process 1296074]
ndof: unknown Logitech product c52b
Read prefs: /home/carlf/.config/blender/2.91/config/userpref.blend
[New Thread 0x7fffed1ed640 (LWP 1296078)]
[New Thread 0x7fffec3ff640 (LWP 1296079)]
[New Thread 0x7fffebbfe640 (LWP 1296080)]
[New Thread 0x7fffeadff640 (LWP 1296081)]
[New Thread 0x7fffda5fe640 (LWP 1296082)]
[New Thread 0x7fffd6a92640 (LWP 1296083)]
[New Thread 0x7fffd5dff640 (LWP 1296084)]
[New Thread 0x7fffd55fe640 (LWP 1296085)]
[New Thread 0x7fffcdf22640 (LWP 1296086)]
[New Thread 0x7fffcd721640 (LWP 1296087)]
[New Thread 0x7fffccf20640 (LWP 1296088)]
[New Thread 0x7fffcc71f640 (LWP 1296089)]
[New Thread 0x7fffcbdfe640 (LWP 1296090)]
[New Thread 0x7fffcb9fd640 (LWP 1296091)]
[New Thread 0x7fffcafff640 (LWP 1296092)]
[New Thread 0x7fffcabfe640 (LWP 1296093)]
[New Thread 0x7fffc9fff640 (LWP 1296094)]
[New Thread 0x7fffc99fe640 (LWP 1296095)]
[New Thread 0x7fffc95fd640 (LWP 1296096)]
[Thread 0x7fffc95fd640 (LWP 1296096) exited]
[New Thread 0x7fffc8bfc640 (LWP 1296097)]
found bundled python: /home/carlf/Downloads/blender-2.91.0-linux64/2.91/python
[New Thread 0x7fffb6334640 (LWP 1296120)]
[Thread 0x7fffb6334640 (LWP 1296120) exited]
[New Thread 0x7fffb6334640 (LWP 1296126)]
[Thread 0x7fffb6334640 (LWP 1296126) exited]

Thread 1 "blender" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
49	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)

"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:

[New Thread 0x7fffb54fd640 (LWP 1301123)]
[Thread 0x7fffb54fd640 (LWP 1301123) exited]

Thread 1 "blender" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
49	in ../sysdeps/unix/sysv/linux/raise.c

I hope that's helpful.

Just now with a brand-new download of 2.91.0. Here's what gdb says: ``` (gdb) run Starting program: /home/carlf/Downloads/blender-2.91.0-linux64/blender [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff6dff640 (LWP 1296064)] [New Thread 0x7ffff3bcf640 (LWP 1296065)] [New Thread 0x7ffff33ce640 (LWP 1296066)] [New Thread 0x7ffff2bcd640 (LWP 1296068)] [New Thread 0x7ffff23cc640 (LWP 1296069)] [New Thread 0x7ffff1bcb640 (LWP 1296070)] [New Thread 0x7ffff13ca640 (LWP 1296071)] [New Thread 0x7ffff0bc9640 (LWP 1296072)] [New Thread 0x7ffff03c8640 (LWP 1296073)] [Detaching after vfork from child process 1296074] ndof: unknown Logitech product c52b Read prefs: /home/carlf/.config/blender/2.91/config/userpref.blend [New Thread 0x7fffed1ed640 (LWP 1296078)] [New Thread 0x7fffec3ff640 (LWP 1296079)] [New Thread 0x7fffebbfe640 (LWP 1296080)] [New Thread 0x7fffeadff640 (LWP 1296081)] [New Thread 0x7fffda5fe640 (LWP 1296082)] [New Thread 0x7fffd6a92640 (LWP 1296083)] [New Thread 0x7fffd5dff640 (LWP 1296084)] [New Thread 0x7fffd55fe640 (LWP 1296085)] [New Thread 0x7fffcdf22640 (LWP 1296086)] [New Thread 0x7fffcd721640 (LWP 1296087)] [New Thread 0x7fffccf20640 (LWP 1296088)] [New Thread 0x7fffcc71f640 (LWP 1296089)] [New Thread 0x7fffcbdfe640 (LWP 1296090)] [New Thread 0x7fffcb9fd640 (LWP 1296091)] [New Thread 0x7fffcafff640 (LWP 1296092)] [New Thread 0x7fffcabfe640 (LWP 1296093)] [New Thread 0x7fffc9fff640 (LWP 1296094)] [New Thread 0x7fffc99fe640 (LWP 1296095)] [New Thread 0x7fffc95fd640 (LWP 1296096)] [Thread 0x7fffc95fd640 (LWP 1296096) exited] [New Thread 0x7fffc8bfc640 (LWP 1296097)] found bundled python: /home/carlf/Downloads/blender-2.91.0-linux64/2.91/python [New Thread 0x7fffb6334640 (LWP 1296120)] [Thread 0x7fffb6334640 (LWP 1296120) exited] [New Thread 0x7fffb6334640 (LWP 1296126)] [Thread 0x7fffb6334640 (LWP 1296126) exited] Thread 1 "blender" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 49 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) ``` "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: ``` [New Thread 0x7fffb54fd640 (LWP 1301123)] [Thread 0x7fffb54fd640 (LWP 1301123) exited] Thread 1 "blender" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 49 in ../sysdeps/unix/sysv/linux/raise.c ``` I hope that's helpful.

Ryan commented

2021-01-02 02:50:22 +01:00

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 like bpy.ops.export_scene.gltf(filepath='~/test.glb').

I also get the same result in gdb.

Entering bt into GDB I get:

Thread 1 "blender" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
49	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
- 0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
- 1  0x00007ffff7872864 in __GI_abort () at abort.c:79
- 2  0x00007ffff4302452 in  () at /lib/x86_64-linux-gnu/libffi.so.8
- 3  0x00007fffc9fdca54 in  ()
    at /home/ry/Downloads/blender-2.91.0-linux64/2.91/python/lib/python3.7/lib-dynload/_ctypes.cpython-37m-x86_64-linux-gnu.so
- 4  0x0000000007176993 in  ()
- 5  0x0000000007177e4c in  ()
#6  0x00007fffc9fd4fe7 in  ()
    at /home/ry/Downloads/blender-2.91.0-linux64/2.91/python/lib/python3.7/lib-dynload/_ctypes.cpython-37m-x86_64-linux-gnu.so
#7  0x00007fffc9fd5179 in  ()
    at /home/ry/Downloads/blender-2.91.0-linux64/2.91/python/lib/python3.7/lib-dynload/_ctypes.cpython-37m-x86_64-linux-gnu.so
- 8  0x000000000719655d in  ()
- 9  0x0000000000e4abe9 in _PyEval_EvalFrameDefault ()
... [truncated]

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!

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 like `bpy.ops.export_scene.gltf(filepath='~/test.glb')`. I also get the same result in `gdb`. Entering `bt` into GDB I get: ``` Thread 1 "blender" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 49 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt - 0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 - 1 0x00007ffff7872864 in __GI_abort () at abort.c:79 - 2 0x00007ffff4302452 in () at /lib/x86_64-linux-gnu/libffi.so.8 - 3 0x00007fffc9fdca54 in () at /home/ry/Downloads/blender-2.91.0-linux64/2.91/python/lib/python3.7/lib-dynload/_ctypes.cpython-37m-x86_64-linux-gnu.so - 4 0x0000000007176993 in () - 5 0x0000000007177e4c in () #6 0x00007fffc9fd4fe7 in () at /home/ry/Downloads/blender-2.91.0-linux64/2.91/python/lib/python3.7/lib-dynload/_ctypes.cpython-37m-x86_64-linux-gnu.so #7 0x00007fffc9fd5179 in () at /home/ry/Downloads/blender-2.91.0-linux64/2.91/python/lib/python3.7/lib-dynload/_ctypes.cpython-37m-x86_64-linux-gnu.so - 8 0x000000000719655d in () - 9 0x0000000000e4abe9 in _PyEval_EvalFrameDefault () ... [truncated] ``` 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!

Robert Guetzkow commented

2021-01-02 10:47:38 +01:00

Added subscriber: @JulienDuroure

Robert Guetzkow commented

2021-01-02 10:47:38 +01:00

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.

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. ](https://builder.blender.org/download/). This is to rule out issues caused by other Python add-ons. @JulienDuroure This could be something for you to look at.

Julien Duroure commented

2021-01-02 13:38:46 +01:00

Hello,
Currently, I can't reproduce neither (tested on stable 2.91 or today's build) on linux Mint

But :

Trying bpy.ops.export_scene.gltf(filepath='/tmp/test.glb') is OK
Trying bpy.ops.export_scene.gltf(filepath='~/test.glb') give an error FileNotFoundError: [Errno 2] No such file or directory: '~/test.glb'

Hello, Currently, I can't reproduce neither (tested on stable 2.91 or today's build) on linux Mint But : - Trying bpy.ops.export_scene.gltf(filepath='/tmp/test.glb') is OK - Trying bpy.ops.export_scene.gltf(filepath='~/test.glb') give an error FileNotFoundError: [Errno 2] No such file or directory: '~/test.glb'

Carl Fink commented

2021-01-02 13:40:08 +01:00

@rjg, Both with 2.91 and the 2.92 alpha, same crash with --factory-startup. Did not try in the debugger.

Robert Guetzkow commented

2021-01-16 15:34:11 +01:00

~~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.~~

~~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.~~

Carl Fink commented

2021-01-16 15:46:45 +01:00

As mentioned, though, the identical thing happens with several non-snap versions.

Robert Guetzkow commented

2021-01-16 16:00:49 +01:00

Right, ignore the previous comment then. Phabricator hides old comments and I missed that we already tested this.

Robert Guetzkow commented

2021-01-20 09:24:52 +01:00

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 in 2.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.

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` in `2.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`.

Carl Fink commented

2021-01-20 12:39:47 +01:00

@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.

@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.

Ryan commented

2021-01-21 01:59:05 +01:00

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

Julien Duroure commented

2021-02-01 08:20:11 +01:00

This is a duplicate of #84752

Robert Guetzkow commented

2021-02-01 10:54:57 +01:00

Closed as duplicate of #84752

Robert Guetzkow closed this issue

2021-02-01 10:54:57 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Import or export of GLB crashes Blender #83685