Page MenuHome

Quitting Blender 2.80 causes a segmentation fault.
Closed, ResolvedPublic

Description

System Information
Operating system: Linux-4.20.16-112.current-x86_64-with-glibc2.9 64 Bits
Graphics card: Radeon 550 Series (POLARIS12, DRM 3.27.0, 4.20.16-112.current, LLVM 8.0.0) X.Org 4.5 (Core Profile) Mesa 19.0.6

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e
Worked: (optional)

Short description of error
When I launch Blender from a terminal there are error messages ( below ) followed by a segmentation fault after Quiting.
I do no work at all in blender when I get this behaviour. Just start it and then quit.

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
Based on the default startup
In a terminal launch blender by navigating to the blender bin directory then enter "./blender" and press Enter.
Then Quit blender. ( File ->Quit).

The startup messages in the terminal are:
Read prefs: /home/psurette/.config/blender/2.80/config/userpref.blend
AL lib: (EE) GetLoadedHrtf: Invalid header in /usr/share/openal/hrtf/default-44100.mhr: "MinPHR02"
AL lib: (EE) GetLoadedHrtf: Failed to load /usr/share/openal/hrtf/default-44100.mhr
AL lib: (EE) GetLoadedHrtf: Invalid header in /usr/share/openal/hrtf/default-48000.mhr: "MinPHR02"
AL lib: (EE) GetLoadedHrtf: Failed to load /usr/share/openal/hrtf/default-48000.mhr
found bundled python: /usr/local/bin/blender-2.80-linux-glibc217-x86_64/2.80/python
Saved session recovery to '/tmp/quit.blend'

After Quitting the messages are:

Blender quit
Segmentation fault

Details

Type
Bug

Event Timeline

Can you run again with:

./blender -noaudio

This will help determine if the OpenAL messages are related to the fault or just warnings.

You can also run blender in debug mode, this will assist in tracing the source of the fault.

./blender --debug

or simply

./blender -d

then post the output here.

Thanks

Brecht Van Lommel (brecht) triaged this task as Needs Information from User priority.Tue, Aug 13, 4:57 AM

Hi,
As requested, the output of blender -noaudio

psurette@barnowl:~/Downloads/blender-2.80-linux-glibc217-x86_64$ ./blender -noaudio
found bundled python: /home/psurette/Downloads/blender-2.80-linux-glibc217-x86_64/2.80/python
Saved session recovery to '/tmp/quit.blend'

Blender quit
Segmentation fault (core dumped)


and the output of blender -d

psurette@barnowl:~/Downloads/blender-2.80-linux-glibc217-x86_64$ ./blender -d
Switching to fully guarded memory allocator.
Blender 2.80 (sub 75)
Build: 2019-07-29 17:17:04 Linux Release
argv[0] = ./blender
argv[1] = -d
read file

Version 280 sub 39 date unknown hash unknown

found bundled python: /home/psurette/Downloads/blender-2.80-linux-glibc217-x86_64/2.80/python
Saved session recovery to '/tmp/quit.blend'

Blender quit
Segmentation fault (core dumped)

Thanks to everyone for your efforts
Paul

gbayliss (gbayliss) added a comment.EditedTue, Aug 13, 8:10 PM

Hi Paul,

Well it doesn't appearto be related to the audio messages, so we can ignore those.

Debug output isn't saying much of interest, it does seem to be missing the "Read prefs:" line, which seems strange.

Also worth checking if there is a crashlog hiding in /tmp/. If not, then you will need to run again with the following command

./blender --debug-all

There will be a lot of output so best to paste into a text file and upload (cloud icon above).

Thanks
Paul

gbayliss (gbayliss) added a comment.EditedTue, Aug 13, 11:29 PM

Unfortunately, that doesn't give us much to go on either.

Just in case there is an issue with your settings, you can try:

./blender --factory-startup

After that I'm afraid options are limited as this is the release version.

You can ensure that your OS and drivers are updated, and retry.

Hi Giles,
I have only run blender "out of the box", that is, without any custom settings.
Here is the output of blender --factory-startup

psurette@barnowl:~/Downloads/blender-2.80-linux-glibc217-x86_64$ ./blender --factory-startup
found bundled python: /home/psurette/Downloads/blender-2.80-linux-glibc217-x86_64/2.80/python
Saved session recovery to '/tmp/quit.blend'

Blender quit
Segmentation fault (core dumped)
psurette@barnowl:~/Downloads/blender-2.80-linux-glibc217-x86_64$

Hope this helps.

Paul

Sorry Paul, I've been offline all day.

I'm running the exact same version (I checked the build time to the second) and I cannot recreate the issue.

If your system uses systemd then I would suggest running:

journalctl -p err -b

Which should help you find any faults since you booted your machine .

With the Radeon RX 550 (Polaris 12 ) chip, you should be awware that it uses switchable graphics. I. e. the display is output is always "generated" with the Intel graphics (this is why it is the only VGA compatible controller in the lspci listing) while you can choose your render device with xrandr. So you would expect to see a fault relating to Intel unless you are specifically setting blender to run using the AMD side.

This video might help https://www.youtube.com/watch?v=7-ckiKQotNw

I can only guess that the fault you are experiencing is something in a driver or something very specific to your system.

Paul Surette (OutRigger1929) claimed this task.

Hi Giles,

Thanks for all of your hard work. I suspect the same as you about my system having an issue. It appears to be the only variable left ( occam's razor ).
I only have one video card installed. My AMD motherboard relies on the cpu to provide a gpu. My Ryzen 7 1700x does not have a gpu included, as verified by xrandr.

I will tinker a bit more and if I find anything useful or not system related I will let you all know.

Thanks again
Regards

Paul