Try enable addon Add Mesh: Extra Object = blender crash #84537

New Issue

Inkabod Chrane · 2021-01-08T20:27:07+01:00

Inkabod Chrane commented

2021-01-08 20:27:07 +01:00

System Information

Operating system: Ubuntu 20.10

Graphics card: AMD RX 5700 XT

Blender Version

Broken:
2.92.0 alpha 2021-01-07 22:28
2.91.0 (2020-11-25 08:34)

Worked: (optional)

Short description of error

When I try and enable the Add Mesh: Extra Object add-on, Blender crashes immediately.

Exact steps for others to reproduce the error

Open a fresh blender file
Go in settings and try to enable Add Mesh: Extra Object
Blender will close abruptly

The default startup will do.

**System Information** Operating system: Ubuntu 20.10 Graphics card: AMD RX 5700 XT **Blender Version** Broken: 2.92.0 alpha 2021-01-07 22:28 2.91.0 (2020-11-25 08:34) Worked: (optional) **Short description of error** When I try and enable the **Add Mesh: Extra Object** add-on, Blender crashes immediately. **Exact steps for others to reproduce the error** 1. Open a fresh blender file 2. Go in settings and try to enable Add Mesh: Extra Object 3. Blender will close abruptly The default startup will do.

Inkabod Chrane commented

2021-01-08 20:27:07 +01:00

Added subscriber: @skittlituted_scorpion

blender-admin commented

2021-01-08 20:27:07 +01:00

blender/blender#84880 was marked as duplicate of this issue

Robert Guetzkow commented

2021-01-08 20:38:05 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2021-01-08 20:38:05 +01:00

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

Robert Guetzkow commented

2021-01-08 20:38:05 +01:00

I cannot reproduce this with the current master. Could you please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

I cannot reproduce this with the current master. Could you please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer). ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)

Inkabod Chrane commented

2021-01-09 12:20:57 +01:00

Hi @rjg, i've just tried with the 2.92 alpha from 2021-01-07 with the gpu debug (i'm on linux Ubuntu) and could not reproduce the bug ... but also the whole instance lagging and after shutting down the instance, i tried to open blender 2.92 normally but could not. The problem is still present in my current blender snap version of 2.91.

Am trying to see if a more up to date version will bug, or if it's just my computer doing weird things.

Sry in advance if it wasn't a bug...

Hi @rjg, i've just tried with the 2.92 alpha from 2021-01-07 with the gpu debug (i'm on linux Ubuntu) and could not reproduce the bug ... but also the whole instance lagging and after shutting down the instance, i tried to open blender 2.92 normally but could not. The problem is still present in my current blender snap version of 2.91. Am trying to see if a more up to date version will bug, or if it's just my computer doing weird things. Sry in advance if it wasn't a bug...

Robert Guetzkow commented

2021-01-09 13:27:03 +01:00

Apologies, I provided the instruction for Windows. Please try to start Blender 2.92 with the following flags:

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

Even if this doesn't crash, please upload the file anyway. Try to start 2.92 normally afterwards, which should crash based on your description, and check if there is a crash log in /tmp. Upload this file as well.

Apologies, I provided the instruction for Windows. Please try to start Blender 2.92 with the following flags: ``` ./blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1 ``` Even if this doesn't crash, please upload the file anyway. Try to start 2.92 normally afterwards, which should crash based on your description, and check if there is a crash log in `/tmp`. Upload this file as well.

Inkabod Chrane commented

2021-01-09 13:42:49 +01:00

blender_debug_output.txt here is what the command dumped when i ran 2.91 (downloaded today) : blender didn't even start // its empty ? it said in the terminal :

$ ./blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1

Aborted (core dumped)

for context, i'm also trying to get OpenCL to work in blender and it isn't going so well ...

[blender_debug_output.txt](https://archive.blender.org/developer/F9557080/blender_debug_output.txt) here is what the command dumped when i ran 2.91 (downloaded today) : blender didn't even start // its empty ? it said in the terminal : $ ./blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1 Aborted (core dumped) for context, i'm also trying to get OpenCL to work in blender and it isn't going so well ...

Inkabod Chrane commented

2021-01-09 16:31:00 +01:00

tried the
./blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1
again on a fresh 2.92 on a fresh ubuntu install, it just dumps core and aborts. The output is empty.

tried the ```./blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1``` again on a fresh 2.92 on a fresh ubuntu install, it just dumps core and aborts. The output is empty.

Inkabod Chrane commented

2021-01-09 18:03:40 +01:00

i've played around a bit and it seems to be on an issue with certain addons in the addons list... some i can activate, some just make blender crash for me.

Inkabod Chrane commented

2021-01-09 18:09:31 +01:00

~/blender-2.92.0-9c074548165a-linux64 $ ./blender --debug --debug-gpu

Switching to fully guarded memory allocator.
Blender 2.92.0 Alpha
Build: 2021-01-09 00:01:36 Linux Release
argv[0] = ./blender
argv[1] = --debug
argv[2] = --debug-gpu
read file 
  Version 280 sub 39 date unknown hash unknown
Info: Deleted 3 object(s)

Warning: add-on "Magic UV": 'wiki_url' in 'bl_info' is deprecated please use 'doc_url' instead!
         /home/padlock/blender-2.92.0-9c074548165a-linux64/2.92/scripts/addons/magic_uv/__init__.py
Aborted (core dumped)

``` ~/blender-2.92.0-9c074548165a-linux64 $ ./blender --debug --debug-gpu Switching to fully guarded memory allocator. Blender 2.92.0 Alpha Build: 2021-01-09 00:01:36 Linux Release argv[0] = ./blender argv[1] = --debug argv[2] = --debug-gpu read file Version 280 sub 39 date unknown hash unknown Info: Deleted 3 object(s) Warning: add-on "Magic UV": 'wiki_url' in 'bl_info' is deprecated please use 'doc_url' instead! /home/padlock/blender-2.92.0-9c074548165a-linux64/2.92/scripts/addons/magic_uv/__init__.py Aborted (core dumped) ```

Inkabod Chrane commented

2021-01-12 14:32:00 +01:00

So, here's some bad news, i have the same issue with exporting gITF. When i click on export/gITF, blender crashes...

Edit: no that works in 2.92. But not the add mesh: extra objects

Edit 2: nope never mind, crashes when i hit export in the export dialogue...

I've also tried it on a different computer, still in Ubuntu, and it also does not work...

So, here's some bad news, i have the same issue with exporting gITF. When i click on export/gITF, blender crashes... Edit: no that works in 2.92. But not the add mesh: extra objects Edit 2: nope never mind, crashes when i hit export in the export dialogue... I've also tried it on a different computer, still in Ubuntu, and it also does not work...

Robert Guetzkow commented

2021-01-12 14:37:51 +01:00

@skittlituted_scorpion Could you please temporarily rename ~/.config/blender/2.92 to something else and try again?

@skittlituted_scorpion Could you please temporarily rename `~/.config/blender/2.92` to something else and try again?

Inkabod Chrane commented

2021-01-12 16:12:41 +01:00

@rjg i've renamed the folder to 2.93, downloaded the latest alpha, and it crashed again ...

tried both the addon crash and the export crash from the terminal debug line, and still nothing in the debug file... just Aborted (core dumped)

to be noted that i'm on a fesh install of Ubuntu, and that when launched with the debug line, Blender is no longer laggy/ frame drops.

@rjg i've renamed the folder to 2.93, downloaded the latest alpha, and it crashed again ... tried both the addon crash and the export crash from the terminal debug line, and still nothing in the debug file... just `Aborted (core dumped)` to be noted that i'm on a fesh install of Ubuntu, and that when launched with the debug line, Blender is no longer laggy/ frame drops.

Mark Kats commented

2021-01-18 04:01:42 +01:00

Added subscriber: @Mkats13

Mark Kats commented

2021-01-18 14:52:45 +01:00

I think I am running into the same issue here... I have a fresh install of Lubuntu on a virtual machine with a fresh 2.91.0 Blender install, and I am trying to install addons, but the enabling of the addon is creating the similar symptoms.

I ran:

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

Went to addons, tried to enable extra objects (as common ground addon) I got the same blank text file as @skittlituted_scorpion received with:
Aborted (core dumped)
For the kicks and giggles, tried to export as gITF, and same thing, same empty report, same core dumped.

I am going to attempt to upload the virtual box, hopefully it helps with troubleshooting and seeing the issue at hand. Password is: Blender
LubuntuBlenderDebug.ova

I think I am running into the same issue here... I have a fresh install of Lubuntu on a virtual machine with a fresh 2.91.0 Blender install, and I am trying to install addons, but the enabling of the addon is creating the similar symptoms. I ran: ``` ./blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1 ``` Went to addons, tried to enable extra objects (as common ground addon) I got the same blank text file as @skittlituted_scorpion received with: ```Aborted (core dumped)``` For the kicks and giggles, tried to export as gITF, and same thing, same empty report, same core dumped. I am going to attempt to upload the virtual box, hopefully it helps with troubleshooting and seeing the issue at hand. Password is: Blender [LubuntuBlenderDebug.ova](https://archive.blender.org/developer/F9583879/LubuntuBlenderDebug.ova)

Robert Guetzkow commented

2021-01-18 14:57:26 +01:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Inkabod Chrane commented

2021-01-18 17:36:54 +01:00

I'm guessing there might be other features that cause a core dump, havn't found any yet.
I'd really like to help find a why to reproduce, but I have no idea where to look ...

I'm guessing there might be other features that cause a core dump, havn't found any yet. I'd really like to help find a why to reproduce, but I have no idea where to look ...

Scurest commented

2021-01-18 20:24:47 +01:00

Added subscriber: @scurest

Scurest commented

2021-01-18 20:24:47 +01:00

Can you open the Python Console and see if import numpy crashes Blender? Someone reported a similar issue on glTF-Blender-IO using Ubuntu 20.10. I see that Add Mesh: Extra Object imports numpy when enabled, and glTF imports numpy when you hit Export, so it'd be consistent.

Can you open the Python Console and see if `import numpy` crashes Blender? Someone reported [a similar issue](https://github.com/KhronosGroup/glTF-Blender-IO/issues/1252) on glTF-Blender-IO using Ubuntu 20.10. I see that Add Mesh: Extra Object imports numpy when enabled, and glTF imports numpy when you hit Export, so it'd be consistent.

Mark Kats commented

2021-01-19 05:46:40 +01:00

You got it @scurest ! Hit the nail right on the head! Crashes the exact same way as exporting or enabling addons!

Scurest commented

2021-01-19 07:45:48 +01:00

Found this: https://askubuntu.com/a/1289381

Simon I. commented

2021-01-19 08:44:13 +01:00

Added subscriber: @Simon_I

Robert Guetzkow commented

2021-01-19 09:50:51 +01:00

@scurest That is an interesting find. We did have issues in the past where Linux distributions build Blender with an incompatible Python version, but those have been addressed (see blender/blender#81688 and related tickets) and also produced a proper stack trace. Although I'm not entirely certain I was also under the impression that the snap package is maintained by us, thus should have the correct dependencies, but I would have to check. If this also happens with official builds as blender/blender#84752 seems to report, a mismatching Python version doesn't appear to be the cause. You can check the currently running Python version by switching to the Scripting workspace and looking at the Python console. It should be 3.7.7 for 2.91, 2.92, 2.93.

@scurest That is an interesting find. We did have issues in the past where Linux distributions build Blender with an incompatible Python version, but those have been addressed (see blender/blender#81688 and related tickets) and also produced a proper stack trace. Although I'm not entirely certain I was also under the impression that the snap package is maintained by us, thus should have the correct dependencies, but I would have to check. If this also happens with official builds as blender/blender#84752 seems to report, a mismatching Python version doesn't appear to be the cause. You can check the currently running Python version by switching to the *Scripting* workspace and looking at the Python console. It should be 3.7.7 for 2.91, 2.92, 2.93.

Simon I. commented

2021-01-19 10:15:31 +01:00

I don't think it's a python version thing, because as reported in blender/blender#84752 it does not happen in the flatpak version, which, as far as I can see, uses the exact same python interpreter as snap and official build: Blender's Python console shows PYTHON INTERACTIVE CONSOLE 3.7.7 (default, Jul 9 2020, 12:52:49) [GCC 9.3.1 20200408 (Red Hat 9.3.1-2)] in all three versions.

I don't think it's a python version thing, because as reported in blender/blender#84752 it does not happen in the flatpak version, which, as far as I can see, uses the exact same python interpreter as snap and official build: Blender's Python console shows `PYTHON INTERACTIVE CONSOLE 3.7.7 (default, Jul 9 2020, 12:52:49) [GCC 9.3.1 20200408 (Red Hat 9.3.1-2)]` in all three versions.

Mark Kats commented

2021-01-20 05:13:35 +01:00

Just spit-balling here (First time trying to help debug something, feel free to tell me to tell me I am wrong) I am looking in the python files the Blender distribution comes with, I see that the numpy version.py file is calling it out as version 1.17.5, I just got done downloading numpy to try check it out and see if I could stumble across something, and when I downloaded it, I got version 1.19.5. Is it possible it just needs the numpy updated? Possibly that all the Linux distributions are using an older numpy?

Robert Guetzkow commented

2021-01-20 09:40:25 +01:00

Added subscriber: @LuisYayo

Robert Guetzkow commented

2021-01-20 09:41:31 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Robert Guetzkow commented

2021-01-20 09:41:31 +01:00

We have a identified a potential cause in blender/blender#84752. Given the similar symptoms, I believe this is the same problem. It 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 blender/blender#84752. Given the similar symptoms, I believe this is the same problem. It 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`.

Inkabod Chrane commented

2021-01-20 12:06:48 +01:00

@rjg @Mkats13 @LuisYayo

Just tried it, commented the CFUNCTYPE(c_int)(lambda: None) in 2.9x/python/lib/python3.7/ctypes/__init__.py.

Seems to have solved it for me.

The add-on and the export worked this time. Used 2.93 version which seemed to have the same issue.

blender_debug_output.txt

I'll keep a look out for any other issue that seem similar, if they ever occur.

@rjg @Mkats13 @LuisYayo Just tried it, commented the `CFUNCTYPE(c_int)(lambda: None)` in `2.9x/python/lib/python3.7/ctypes/__init__.py`. Seems to have solved it for me. The add-on and the export worked this time. Used `2.93 version` which seemed to have the same issue. [blender_debug_output.txt](https://archive.blender.org/developer/F9589324/blender_debug_output.txt) I'll keep a look out for any other issue that seem similar, if they ever occur.

Robert Guetzkow commented

2021-01-20 12:10:36 +01:00

Closed as duplicate of blender/blender#84752

Robert Guetzkow closed this issue

2021-01-20 12:10:36 +01:00

Sign in to join this conversation.