Crash when accessing extra tracking settings #40147

New Issue

Igor Valorin · 2014-05-11T23:21:40+02:00

Igor Valorin commented

2014-05-11 23:21:40 +02:00

System Information
Arch Linux x86_64 updated daily
Linux kernel 3.14.3
CPU Intel Core 2 Q6600
RAM 6 GB
GPU nVidia GeForce GT640

Blender Version
Git master hash df74230

Short description of error

Exact steps for others to reproduce the error
See attached screenshots. The mouse cursor shows exact location where to press to get segmentation fault.

motion_tracking_extra_settings_crash.blend

And link to the video used in the blend file: Planar tracking source video

**System Information** Arch Linux x86_64 updated daily Linux kernel 3.14.3 CPU Intel Core 2 Q6600 RAM 6 GB GPU nVidia GeForce GT640 **Blender Version** Git master hash df74230 **Short description of error** **Exact steps for others to reproduce the error** See attached screenshots. The mouse cursor shows exact location where to press to get segmentation fault. ![motion_tracking_extra_settings_crash-1.png](https://archive.blender.org/developer/F88525/motion_tracking_extra_settings_crash-1.png) ![motion_tracking_extra_settings_crash-2.png](https://archive.blender.org/developer/F88527/motion_tracking_extra_settings_crash-2.png) [motion_tracking_extra_settings_crash.blend](https://archive.blender.org/developer/F88529/motion_tracking_extra_settings_crash.blend) And link to the video used in the blend file: [Planar tracking source video ](https://www.youtube.com/watch?v=F0hxLemXRDU)

Igor Valorin commented

2014-05-11 23:21:40 +02:00

Changed status to: 'Open'

Igor Valorin commented

2014-05-11 23:21:40 +02:00

Added subscriber: @igvalor2

Igor Valorin commented

2014-05-12 02:31:03 +02:00

The bug is much more disasterous! It also affects some other interface parts. For example:

Open Blender and stay in default scene.
Add a plane.
In the left tool panel check "Align to view" checkbox.
Segmentation fault.

The bug is much more disasterous! It also affects some other interface parts. For example: 1. Open Blender and stay in default scene. 2. Add a plane. 3. In the left tool panel check "Align to view" checkbox. 4. Segmentation fault.

Willi commented

2014-05-12 13:19:45 +02:00

Added subscriber: @willi-2

Willi commented

2014-05-12 13:19:45 +02:00

Strange. I can not reproduce with the latter steps on Win7/64 (tried 1464316 (May 9) and 47e9057 (May 12)).

EDIT: Also not reproducible on Kubuntu (inside VM) with version 5db81a0

Strange. I can not reproduce with the latter steps on Win7/64 (tried 1464316 (May 9) and 47e9057 (May 12)). EDIT: Also not reproducible on Kubuntu (inside VM) with version 5db81a0

Sergey Sharybin commented

2014-05-12 15:05:21 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-05-12 15:05:21 +02:00

@igvalor2, can not reproduce it either. Please check whether it's still an issue for you with the latest build from buildbot.

Igor Valorin commented

2014-05-12 20:26:32 +02:00

Maybe trace helps
motion_tracking_extra_settings_crash.crash.txt
Hash 1b1b71f

Maybe trace helps [motion_tracking_extra_settings_crash.crash.txt](https://archive.blender.org/developer/F88702/motion_tracking_extra_settings_crash.crash.txt) Hash 1b1b71f

Sergey Sharybin commented

2014-05-12 20:29:06 +02:00

Not really. And seems it's not latest buildbot build?

Igor Valorin commented

2014-05-12 20:30:04 +02:00

I build myself using CMake

Last time I reported crash, Campbell Barton resolved the issue really quickly

I build myself using CMake Last time I reported crash, Campbell Barton resolved the issue really quickly

Igor Valorin commented

2014-05-12 22:34:29 +02:00

OK. Downloaded last build from buildbot (2014-05-12 hash 47e9057) and it's working. Looks like the problem is current Arch Linux specific.

OK. Downloaded last build from buildbot (2014-05-12 hash 47e9057) and it's working. Looks like the problem is current Arch Linux specific.

Igor Valorin commented

2014-05-12 22:47:07 +02:00

Probably my cmake cache file would help
CMakeCache.txt

Probably my cmake cache file would help [CMakeCache.txt](https://archive.blender.org/developer/F88724/CMakeCache.txt)

Campbell Barton commented

2014-05-13 12:20:04 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2014-05-13 12:20:04 +02:00

Cant redo this bug, and valgrind reports no issues.

Igor Valorin commented

2014-05-13 22:51:54 +02:00

Will core dump with my binary help? If they will how should I hand them over to you?

Igor Valorin commented

2014-05-14 02:31:34 +02:00

So, here are some results of my investigation.
Blender works again for me, when I compile it with compiler optimization flag -O1 or even without it. If I build with -O2 or -O3, Blender crashes.

I use
GCC 4.9
LLVM/Clang 3.4.1

Before May 12 everything worked with -O3. I'm puzzled.

Probably also my pacman upgrade log may make some help (cut to last several days)

pacman.recent.log

So, here are some results of my investigation. Blender works again for me, when I compile it with compiler optimization flag -O1 or even without it. If I build with -O2 or -O3, Blender crashes. I use GCC 4.9 LLVM/Clang 3.4.1 Before May 12 everything worked with -O3. I'm puzzled. Probably also my pacman upgrade log may make some help (cut to last several days) [pacman.recent.log](https://archive.blender.org/developer/F88892/pacman.recent.log)

Sergey Sharybin commented

2014-05-14 11:28:48 +02:00

Using -O3 is really asking for troubles, don't use it. And it seems to be rather a compiler issue. Try using gcc-4.7 which is what official builds are created with.

Igor Valorin commented

2014-05-14 11:46:27 +02:00

GCC 4.7 is not an option for me. As I said, before May 12 -O3 worked fine with GCC 4.9, now even -O2 makes crashy executable. For the time I'll settle on what works: -O1. I hope you will investigate and resolve this nasty issue.

Sergey Sharybin commented

2014-05-14 11:57:14 +02:00

I'm not sure why gcc-4.7 is not an option for you in purposes of testing. Compiling with this gcc version would show whether it's a general issue in our code or it's just bug in some particular gcc version. We obviously can't fix bugs in compilers..

Also, you're building from sources and that's real cool. So what you can do is to find a revision which worked for you. You can use git checkout <COMMIT_SHA> to check whether this hash worked fine.

Then if you'll find a commit which worked for you you can do this:
$ git checkout master
$ git bisect start
$ git bisect bad
$ git bisect good COMMIT_SHA_WHICH_WORKED_FOR_YOU

it'll start bisecting process. So you build blender and check if it works. If it works you type git bisect good if it crashes you type git bisect bad. If some compilation error happens you can type git bisect skip. Do this for until commit which broke gcc for you is found.

Once you spot the buggy commit, please report back and this would give some clues to us hopefully.

I'm not sure why gcc-4.7 is not an option for you in purposes of testing. Compiling with this gcc version would show whether it's a general issue in our code or it's just bug in some particular gcc version. We obviously can't fix bugs in compilers.. Also, you're building from sources and that's real cool. So what you can do is to find a revision which worked for you. You can use `git checkout <COMMIT_SHA>` to check whether this hash worked fine. Then if you'll find a commit which worked for you you can do this: $ git checkout master $ git bisect start $ git bisect bad $ git bisect good COMMIT_SHA_WHICH_WORKED_FOR_YOU it'll start bisecting process. So you build blender and check if it works. If it works you type `git bisect good` if it crashes you type `git bisect bad`. If some compilation error happens you can type `git bisect skip`. Do this for until commit which broke gcc for you is found. Once you spot the buggy commit, please report back and this would give some clues to us hopefully.

Igor Valorin commented

2014-05-14 12:15:43 +02:00

4.7 is not an option, because Arch Linux is a so called "rolling release" guy. Installing GCC 4.7 means doing it from source into separate directory being at risk to mess the versions, which I just don't want to mess with. Not to mention building the monster from source is a daunting timespending.

About git bisect - I'll try it. Thanks for the hint.

4.7 is not an option, because Arch Linux is a so called "rolling release" guy. Installing GCC 4.7 means doing it from source into separate directory being at risk to mess the versions, which I just don't want to mess with. Not to mention building the monster from source is a daunting timespending. About git bisect - I'll try it. Thanks for the hint.

Igor Valorin commented

2014-05-15 04:47:16 +02:00

After playing with git bisect I downgraded the Blender source down to commit from April 27 and my problem persisted. Blender still crashes when I use -O2 or -O3 optimization flags. So looks like the problem is really environment specific. If anyone of Blender devs uses Arch Linux and has working Blender built with GCC 4.9 and -O3, please share CMake cache file or Scons config and Pacman log file, so I could compare. Campbell Barton?

For now I'm going to use -O1. At least it works.

After playing with git bisect I downgraded the Blender source down to commit from April 27 and my problem persisted. Blender still crashes when I use -O2 or -O3 optimization flags. So looks like the problem is really environment specific. If anyone of Blender devs uses Arch Linux and has working Blender built with GCC 4.9 and -O3, please share CMake cache file or Scons config and Pacman log file, so I could compare. Campbell Barton? For now I'm going to use -O1. At least it works.

Sergey Sharybin commented

2014-05-15 10:58:42 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2014-05-15 10:58:42 +02:00

Sergey Sharybin self-assigned this 2014-05-15 10:58:42 +02:00

Sergey Sharybin commented

2014-05-15 10:58:42 +02:00

If it's worked before and doesn't work now then it's likely update of gcc caused this and you'd better poke gcc maintainers in arch. But you're also welcome to ask for the help in our ML and IRC (see http://www.blender.org/get-involved/developers/).

Bug tracker is meant to be used to report bugs which are reproducible in official builds. If it ends up setu-specific we handle it outside of the tracker.

So thanks for the report, but closing it now.

If it's worked before and doesn't work now then it's likely update of gcc caused this and you'd better poke gcc maintainers in arch. But you're also welcome to ask for the help in our ML and IRC (see http://www.blender.org/get-involved/developers/). Bug tracker is meant to be used to report bugs which are reproducible in official builds. If it ends up setu-specific we handle it outside of the tracker. So thanks for the report, but closing it now.

Igor Valorin commented

2014-05-18 14:10:00 +02:00

SOLVED by using clang instead of gcc and clang++ instead of g++!

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

Crash when accessing extra tracking settings #40147