Metaball objects selection - Crash #39294

New Issue

Kalina Attila · 2014-03-20T20:15:44+01:00

Kalina Attila commented

2014-03-20 20:15:44 +01:00

System Information
Ubuntui Saucy
ATI Radeon HD5750 (proprietary driver)

Blender Version
Broken: 2.70
fresh release from official site

Short description of error

Blender crashes to desktop after trying to select any metaball object while in wireframe mode.

Exact steps for others to reproduce the error

Add any type of Metaball object to scene.
switch to wireframe in the viewport.
try selecting the Metaball object.

**System Information** Ubuntui Saucy ATI Radeon HD5750 (proprietary driver) **Blender Version** Broken: 2.70 fresh release from official site **Short description of error** Blender crashes to desktop after trying to select any metaball object while in wireframe mode. **Exact steps for others to reproduce the error** 1. Add any type of Metaball object to scene. 2. switch to wireframe in the viewport. 3. try selecting the Metaball object.

Kalina Attila commented

2014-03-20 20:15:44 +01:00

Changed status to: 'Open'

Kalina Attila commented

2014-03-20 20:15:44 +01:00

Added subscriber: @Sinnorfin

Bastien Montagne commented

2014-03-20 20:51:58 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2014-03-20 20:51:58 +01:00

Cannot reproduce that here (debian64 testing, HD5730M free driver)…

You should get a crash file generated by Blender (run it from a terminal to see were it is saved, usually /tmp/...), please attach it here.

Also you say “fresh release from official site”, I assume you are talking about blender.org, not ubuntu's package?

Cannot reproduce that here (debian64 testing, HD5730M free driver)… You should get a crash file generated by Blender (run it from a terminal to see were it is saved, usually /tmp/...), please attach it here. Also you say “fresh release from official site”, I assume you are talking about blender.org, not ubuntu's package?

Kalina Attila commented

2014-03-20 21:08:24 +01:00

Yes 2.70 version from blender.org.

Ran with GDB:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7e03c92 in ?? ()

Edit: Windows 64bit version doesnt reproduce the crash.

Yes 2.70 version from blender.org. Ran with GDB: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7e03c92 in ?? () Edit: Windows 64bit version doesnt reproduce the crash.

Bastien Montagne commented

2014-03-20 21:34:05 +01:00

Eeeeh… rather a short backtrace in that crash log… :/

Thanks for the file anyway. I guess running bt in gdb after the crash does not say more?

Eeeeh… rather a short backtrace in that crash log… :/ Thanks for the file anyway. I guess running `bt` in gdb after the crash does not say more?

Kalina Attila commented

2014-03-20 21:42:40 +01:00

"Eeeeh… rather a short backtrace in that crash log… :/"

Sorry, first time reporting, what does short backtrace means? should i do more tasks with blender before inducing the crash?
It crashes in whatever period of the work, if i select a metaball object in wireframe(pressing Z) it crashes. Even on vanilla scene.

bt in gdb gives this:

0 0x00007ffff7e03c92 in ?? ()
1 0x0000001c00000000 in ?? ()
2 0x0000000000000000 in ?? ()

"Eeeeh… rather a short backtrace in that crash log… :/" Sorry, first time reporting, what does short backtrace means? should i do more tasks with blender before inducing the crash? It crashes in whatever period of the work, if i select a metaball object in wireframe(pressing Z) it crashes. Even on vanilla scene. bt in gdb gives this: - 0 0x00007ffff7e03c92 in ?? () - 1 0x0000001c00000000 in ?? () - 2 0x0000000000000000 in ?? ()

Bastien Montagne commented

2014-03-20 21:49:23 +01:00

Ah, sorry :)

“Short backtrace” means that there are very few steps between the "entry point" of the application and the crash (here, we only have three, which is confirmed by the output of gdb's bt command, which also stands for "back trace"), so was just a mere comment on the issue - it’s not common in Blender, crashes often happen after ten or more steps… ;)

Think you have given us all data you could, I just can’t reproduce the issue myself… Guess we’ll have to wait and see whether other devs can reproduce it, or have an idea about that bug!

Ah, sorry :) “Short backtrace” means that there are very few steps between the "entry point" of the application and the crash (here, we only have three, which is confirmed by the output of gdb's bt command, which also stands for "back trace"), so was just a mere comment on the issue - it’s not common in Blender, crashes often happen after ten or more steps… ;) Think you have given us all data you could, I just can’t reproduce the issue myself… Guess we’ll have to wait and see whether other devs can reproduce it, or have an idea about that bug!

Bastien Montagne commented

2014-03-20 21:52:42 +01:00

Added subscriber: @Sergey

Bastien Montagne commented

2014-03-20 21:52:42 +01:00

Adding Sergey as CC, since he is maintainer of metaballs I think?

Btw, I thought about two more tests you can make:

Try launching blender with -t1 option (to get mono-threaded update instead of multi-threaded one).
And did you checked all other primitive types? meshes of course, but also curves, surfaces, text?

Adding Sergey as CC, since he is maintainer of metaballs I think? Btw, I thought about two more tests you can make: * Try launching blender with `-t1` option (to get mono-threaded update instead of multi-threaded one). * And did you checked all other primitive types? meshes of course, but also curves, surfaces, text?

Kalina Attila commented

2014-03-20 21:59:52 +01:00

Ah,ok,thanks for clarifying:)

Launching with -t1 resulted in the same crash. (metaballs selected in wireframe view)
other primitive types doesnt crash under these circumstances.

Ah,ok,thanks for clarifying:) - Launching with -t1 resulted in the same crash. (metaballs selected in wireframe view) - other primitive types doesnt crash under these circumstances.

Fasit commented

2014-03-21 04:45:16 +01:00

Added subscriber: @ygtsvtr

Fasit commented

2014-03-21 04:45:16 +01:00

caNT reproduce . win 7 64 bit.Tested on official 270 and #3406ef8

Sergey Sharybin commented

2014-03-21 08:56:54 +01:00

Can not reproduce the crash as well.

Try using blender-softwaregl script for the official archive and see whether you can reproduce the crash then. This script launches blender in fully software opengl mode, which eliminates probability of bugs in your video driver.

Can not reproduce the crash as well. Try using blender-softwaregl script for the official archive and see whether you can reproduce the crash then. This script launches blender in fully software opengl mode, which eliminates probability of bugs in your video driver.

Kalina Attila commented

2014-03-21 13:06:13 +01:00

Crash cant be reproduced in software opengl mode, selection works as intended. So it's a video driver bug then?

Installing the Opensource drivers made the problem disappear.

Crash cant be reproduced in software opengl mode, selection works as intended. So it's a video driver bug then? Installing the Opensource drivers made the problem disappear.

Sergey Sharybin commented

2014-03-21 13:45:51 +01:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2014-03-21 13:45:51 +01:00

Sergey Sharybin self-assigned this 2014-03-21 13:45:51 +01:00

Sergey Sharybin commented

2014-03-21 13:45:51 +01:00

Its likely the video driver issue then which we can't really fix. Sorry, but we can't fix bugs in proprietary AMD drivers..Thanks for the report anyway!

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

Metaball objects selection - Crash #39294