Floating point exception (crash) when switching to Edit mode #72387

New Issue

Amaral Krichman · 2019-12-12T14:21:28+01:00

Amaral Krichman commented

2019-12-12 14:21:28 +01:00

System Information
Operating system: Linux-5.3.0-23-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: AMD BONAIRE (DRM 2.50.0, 5.3.0-23-generic, LLVM 9.0.1) X.Org 4.5 (Core Profile) Mesa 20.0.0-devel (git-8259c97 2019-12-07 eoan-oibaf-ppa)

Blender Version
Broken: version: 2.82 (sub 5), branch: master, commit date: 2019-12-11 18:53, hash: b03066f7ee

Short description of error
Blender starts normally, the minute I try to switch to edit mode, be it via hotkeys, calling the operator from the search menu or just switching from the mode list, it crashes. Other modes work just fine.
I've tried with --factory-startup but the results are the same.

I'm starting to think that perhaps it's something I might have done on my end with Ubuntu? Could that be possible?
Clearly something's not working in blender, but I can run 2.82, 2.81a and 2.81 just fine from Windows, and until fairly recently, (before it started crashing on #72258) I was running 2.81 just fine in Linux too.

Exact steps for others to reproduce the error
Enter editmode

I'm including system info and my config files.
system-info.txt

Edit: I removed the config files and keymap related stuff to avoid confusion. The debug-gpu log is in the comments.

**System Information** Operating system: Linux-5.3.0-23-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: AMD BONAIRE (DRM 2.50.0, 5.3.0-23-generic, LLVM 9.0.1) X.Org 4.5 (Core Profile) Mesa 20.0.0-devel (git-8259c97 2019-12-07 eoan-oibaf-ppa) **Blender Version** Broken: version: 2.82 (sub 5), branch: master, commit date: 2019-12-11 18:53, hash: `b03066f7ee` **Short description of error** Blender starts normally, the minute I try to switch to edit mode, be it via hotkeys, calling the operator from the search menu or just switching from the mode list, it crashes. Other modes work just fine. I've tried with `--factory-startup` but the results are the same. I'm starting to think that perhaps it's something I might have done on my end with Ubuntu? Could that be possible? Clearly something's not working in blender, but I can run 2.82, 2.81a and 2.81 just fine from Windows, and until fairly recently, (before it started crashing on #72258) I was running 2.81 just fine in Linux too. **Exact steps for others to reproduce the error** Enter editmode I'm including system info and my config files. [system-info.txt](https://archive.blender.org/developer/F8212653/system-info.txt) *Edit: I removed the config files and keymap related stuff to avoid confusion. The debug-gpu log is in the comments.*

Amaral Krichman commented

2019-12-12 14:21:28 +01:00

Added subscriber: @karmaral

blender-admin commented

2019-12-12 14:21:28 +01:00

#72885 was marked as duplicate of this issue

Germano Cavalcante commented

2019-12-16 13:13:40 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-12-16 13:13:40 +01:00

Is the custom keymap related to cash?
To find out, try after loading Factory Settings. (File -> Defaults -> Load Factory Settings)
If it is not related, this information will only hinder.

Also try to run blender_debug-gpu.cmd that is included in the download. After Blender closes, the logs will be in a text file which can be attached here.

Is the custom keymap related to cash? To find out, try after loading Factory Settings. (`File -> Defaults -> Load Factory Settings`) If it is not related, this information will only hinder. Also try to run `blender_debug-gpu.cmd` that is included in the download. After Blender closes, the logs will be in a text file which can be attached here.

Amaral Krichman commented

2019-12-18 18:33:38 +01:00

In #72387#829491, @mano-wii wrote:
Is the custom keymap related to cash?
To find out, try after loading Factory Settings. (File -> Defaults -> Load Factory Settings)
If it is not related, this information will only hinder..

It seems it isn't. I only included it because both errors started happening simultaneously. I will edit the post appropiately then.

Also try to run blender_debug-gpu.cmd that is included in the download. After Blender closes, the logs will be in a text file which can be attached here.

What download? I don't have such file, but it should be the same as -d --debug-gpu , right?gpu-dump.txt

After peeking the logs I bit, I tried switching to editmode with overlays disabled, and this time it didn't crash. As soon as I turn them back on while in editmode, it crashes. I suppose that narrows it down a bit.

> In #72387#829491, @mano-wii wrote: > Is the custom keymap related to cash? > To find out, try after loading Factory Settings. (`File -> Defaults -> Load Factory Settings`) > If it is not related, this information will only hinder.. It seems it isn't. I only included it because both errors started happening simultaneously. I will edit the post appropiately then. > Also try to run `blender_debug-gpu.cmd` that is included in the download. After Blender closes, the logs will be in a text file which can be attached here. What download? I don't have such file, but it should be the same as `-d --debug-gpu` , right?[gpu-dump.txt](https://archive.blender.org/developer/F8232545/gpu-dump.txt) After peeking the logs I bit, I tried switching to editmode with overlays disabled, and this time it didn't crash. As soon as I turn them back on while in editmode, it crashes. I suppose that narrows it down a bit.

Alan Troth commented

2019-12-19 18:28:41 +01:00

Added subscriber: @AlanT

Alan Troth commented

2019-12-19 18:28:41 +01:00

I've been having similar problems and I think there are enough similarities for me to mention them here.

Downloaded blender crashes when run. When run from a terminal I get a Division by Zero error.
A locally compiled version of blender runs but when I go into edit mode it crashes (deep inside glFlush()).
The locally compiled version doesn't crash if I disable overlays.
I also had a feeling it was something to do with my system because my locally compiled version was working and then stopped working without me git pulling/rebasing.
I'm using an AMD GCN2 (Sea Islands family) based video card - Hawaii (Bonaire is also GCN2).

I've fixed (side stepped?) the crash by switching from radeon drivers to amdgpu drivers. Switching back to radeon drivers causes blender to crash again.

I'm using Arch Linux and used these links for information on switching drivers:

R9 390 (Hawaii) series poor performance and/or instability
Enable Southern Islands (SI) and Sea Islands (CIK) support

I hope this helps you with your crash.

system-info.txt dump.txt

I've been having similar problems and I think there are enough similarities for me to mention them here. - Downloaded blender crashes when run. When run from a terminal I get a Division by Zero error. - A locally compiled version of blender runs but when I go into edit mode it crashes (deep inside glFlush()). - The locally compiled version doesn't crash if I disable overlays. - I also had a feeling it was something to do with my system because my locally compiled version was working and then stopped working without me git pulling/rebasing. - I'm using an AMD GCN2 (Sea Islands family) based video card - Hawaii (Bonaire is also GCN2). I've fixed (side stepped?) the crash by switching from radeon drivers to amdgpu drivers. Switching back to radeon drivers causes blender to crash again. I'm using Arch Linux and used these links for information on switching drivers: [R9 390 (Hawaii) series poor performance and/or instability ](https://wiki.archlinux.org/index.php/AMDGPU#R9_390_series_poor_performance_and/or_instability) [Enable Southern Islands (SI) and Sea Islands (CIK) support ](https://wiki.archlinux.org/index.php/AMDGPU#Enable_Southern_Islands_(SI)_and_Sea_Islands_(CIK)_support) I hope this helps you with your crash. [system-info.txt](https://archive.blender.org/developer/F8234775/system-info.txt) [dump.txt](https://archive.blender.org/developer/F8234777/dump.txt)

Germano Cavalcante commented

2019-12-20 16:45:11 +01:00

The dump file does not indicate much.
What is displayed if the option is just --debug?

The dump file does not indicate much. What is displayed if the option is just `--debug`?

Alan Troth commented

2019-12-20 17:48:52 +01:00

My original dump file was when running blender from the command line where it crashes straight away.

Dump file from the command line with just --debug:
cmd --debug dump.txt

Running debug in Qt Creator where the crash happens when entering edit mode:
QtCreator dump.txt

My original dump file was when running blender from the command line where it crashes straight away. Dump file from the command line with just --debug: [cmd --debug dump.txt](https://archive.blender.org/developer/F8237696/cmd_--debug_dump.txt) Running debug in Qt Creator where the crash happens when entering edit mode: [QtCreator dump.txt](https://archive.blender.org/developer/F8237698/QtCreator_dump.txt)

Germano Cavalcante commented

2019-12-20 18:09:13 +01:00

This is a driver problem.
In fact it seems to be a problem deep inside glFlush().
It would take a lot of trial and error outside the OpenGL API to understand what in blender results in this problem.
But this requires a developer with knowledge of this subject and the same setup available.

This can be hard to achieve.

This is a driver problem. In fact it seems to be a problem deep inside `glFlush()`. It would take a lot of trial and error outside the OpenGL API to understand what in blender results in this problem. But this requires a developer with knowledge of this subject and the same setup available. This can be hard to achieve.

Georg K commented

2019-12-29 21:41:27 +01:00

Added subscriber: @georgK

Georg K commented

2019-12-29 21:41:27 +01:00

Operating system: Linux-5.4.6-2-MANJARO-x86_64-with-glibc2.29 64 Bits
Graphics card: AMD VERDE (DRM 2.50.0, 5.4.6-2-MANJARO, LLVM 9.0.0) X.Org 4.5 (Core Profile) Mesa 19.3.1

Blender Version
Broken: version: 2.82 (sub 4), branch: master (modified), commit date: 2019-12-10 16:09, hash: 4fa774b533
Worked: the same version worked before manjaro update

Seems like I am also affected:
After the latest manjaro update: [Stable Update] 2019-12-29 that brought mesa up to v 19.3.1-1, the new Blender 17:2.81.a-3 version does not work at all, it crashes at startup - the old version worked without problems. My own build is starting, but crashes with "Floating point exception (core dumped)" when switching to Material preview or Eevee rendered preview - and, like Al reported, when entering Edit mode.

It may be a coincidence, but so far it seems that older AMD gpus are affected (Verde from early 2012, Bonaire early 2013, Hawaii late 2013).

Unfortunately, there seems to be no core dump neither in /tmp nor in the folder that I configured for "Temporary Files".
Now I can't work with Blender at all anymore, so this is really important to me, please fix it.

Operating system: Linux-5.4.6-2-MANJARO-x86_64-with-glibc2.29 64 Bits Graphics card: AMD VERDE (DRM 2.50.0, 5.4.6-2-MANJARO, LLVM 9.0.0) X.Org 4.5 (Core Profile) Mesa 19.3.1 **Blender Version** Broken: version: 2.82 (sub 4), branch: master (modified), commit date: 2019-12-10 16:09, hash: `4fa774b533` Worked: the same version worked before manjaro update Seems like I am also affected: After the latest manjaro update: [Stable Update] 2019-12-29 that brought mesa up to v 19.3.1-1, the new Blender 17:2.81.a-3 version does not work at all, it crashes at startup - the old version worked without problems. My own build is starting, but crashes with "Floating point exception (core dumped)" when switching to Material preview or Eevee rendered preview - and, like Al reported, when entering Edit mode. It may be a coincidence, but so far it seems that older AMD gpus are affected (Verde from early 2012, Bonaire early 2013, Hawaii late 2013). Unfortunately, there seems to be no core dump neither in /tmp nor in the folder that I configured for "Temporary Files". Now I can't work with Blender at all anymore, so this is really important to me, please fix it.

Rich commented

2020-01-03 18:03:15 +01:00

Added subscriber: @seacrow

Rich commented

2020-01-03 18:03:15 +01:00

Operating System: Manjaro Linux
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0
Kernel Version: 5.4.6-2-MANJARO
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz
Memory: 7.7 GiB of RAM

I am having same problem as Georg K.

"Floating point exception (core dumped)" at startup

nor is there anything in tmp to help

First post here so forgive me if I am not following usual protocol.

Thanks

Operating System: Manjaro Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Kernel Version: 5.4.6-2-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz Memory: 7.7 GiB of RAM I am having same problem as Georg K. "Floating point exception (core dumped)" at startup nor is there anything in tmp to help First post here so forgive me if I am not following usual protocol. Thanks

Georg K commented

2020-01-03 18:24:26 +01:00

Added subscriber: @Richard-Kubusch

Georg K commented

2020-01-03 18:24:26 +01:00

@seacrow:
Guess you are one of the lucky owners of older AMD graphics as well?
I bypassed the problem by downgrading mesa. Also Blender 2.79 https://download.blender.org/release/Blender2.79/latest/ is still working (but segfaults opening 2.82 projects). Those are no solutions in the longer term, but at least we can continue our projects.

@seacrow: Guess you are one of the lucky owners of older AMD graphics as well? I bypassed the problem by downgrading mesa. Also Blender 2.79 https://download.blender.org/release/Blender2.79/latest/ is still working (but segfaults opening 2.82 projects). Those are no solutions in the longer term, but at least we can continue our projects.

Rich commented

2020-01-03 18:38:07 +01:00

@georgK

Thanks for this.
I'll downgrade mesa.
I was just getting used to Blender 2.82!!

Guess I need to swap out my graphics card if I can scavenge one from my son!

@georgK Thanks for this. I'll downgrade mesa. I was just getting used to Blender 2.82!! Guess I need to swap out my graphics card if I can scavenge one from my son!

Jeroen Bakker commented

2020-01-06 12:43:39 +01:00

Added subscribers: @Kronstoeckel, @StephenSwaney

Amaral Krichman commented

2020-01-07 20:25:52 +01:00

Well. I'm not sure what happened, but a bunch of things got updated via the Software Updater and now everything seems to be working. No crash so far, and the older versions that were previously broken are back.

Here's the list of things. Obviously drivers, but I can't discern much.
update log.txt

I'm using 2.82 3a35301fd1 and no crash when entering editmode so far.
Here's the system info just in case.
system-info.txt

Well. I'm not sure what happened, but a bunch of things got updated via the Software Updater and now everything seems to be working. No crash so far, and the older versions that were previously broken are back. Here's the list of things. Obviously drivers, but I can't discern much. [update log.txt](https://archive.blender.org/developer/F8264717/update_log.txt) I'm using 2.82 3a35301fd16d and no crash when entering editmode so far. Here's the system info just in case. [system-info.txt](https://archive.blender.org/developer/F8264720/system-info.txt)

Alan Troth commented

2020-01-13 15:08:20 +01:00

Since my latest system update blender is working again.

Stephen Swaney commented

2020-01-13 15:56:35 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Stephen Swaney closed this issue

2020-01-13 15:56:35 +01:00

Stephen Swaney self-assigned this 2020-01-13 15:56:35 +01:00

Stephen Swaney commented

2020-01-13 15:56:35 +01:00

Sounds like everything is working after system software updates.
Closing

Sounds like everything is working after system software updates. Closing

Georg K commented

2020-01-13 18:06:02 +01:00

On manjaro stable, the latest Mesa is still 19.3.1-1 from 18.Dec 2019.
What version of Mesa solved it?

On manjaro stable, the latest Mesa is still 19.3.1-1 from 18.Dec 2019. What version of Mesa solved it?

Alan Troth commented

2020-01-13 19:51:50 +01:00

I updated my Arch Linux today and got 19.3.2-1

Georg K commented

2020-01-13 20:44:04 +01:00

Thank you, guess I will have to wait two weeks until it lands on Manjaro, too.
edit:
Solved on Manjaro as well as of 16.1.2020 (upgraded to Mesa 19.3.2-2)

Thank you, guess I will have to wait two weeks until it lands on Manjaro, too. edit: Solved on Manjaro as well as of 16.1.2020 (upgraded to Mesa 19.3.2-2)

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

Floating point exception (crash) when switching to Edit mode #72387