RViz crash when saving files

[fersarr]

Hi, I have been using rqt-rviz to see the data from my kinect (via openni) but everytime I try to save a file, any kind (image, configuration file,etc.) the "save as..." window opens but it doesnt load nor say anything, just gray. And my ubuntu screen gets darker (like when programs crash). When I type CTRL-C in the terminal to kill rqt-rviz I get this error:

[ INFO] [1365896813.550288513]: OpenGl version: 3.0 (GLSL 1.3).
python: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
python: /usr/include/boost/thread/pthread/recursive_mutex.hpp:92: boost::recursive_mutex::~recursive_mutex(): Assertion `!pthread_mutex_destroy(&m)' failed.
Aborted (core dumped)

But that message does not appear if I was using rviz alone (no rqt). But it does crash in both ways. Heres a screenshot

http://s3.postimg.org/mu8o1k2oi/Screenshot3.jpg

There is no problem iwhen I try to save if I I had not launched openni first

[dgossow]

Probably the DepthCloud Display is blocking the main thread. I've had this happen on my machine as well when Kinect data comes in at full 30Hz.

We might do something with the scheduling to make sure that calling update() on all Displays doesn't flood the main thread in case that's the reason, or if it is something specific about how the DepthCloud Display does it's thing we should fix that (maybe a mutex inside a Qt event handler?).

attn @jkammerl

[jkammerl]

There is a locked mutex in the "update" and " clear" method.
"clear" gets also called during "onDisable". If this is a problem, I think there is a way to remove this mutex!

@fersarr could you provide a stack trace? This would help tracking down this issue.

[dgossow]

If that's the problem, it's going to be the "update" mutex.

[fersarr]

I tried to get you the stack trace but I only get "core dumped" when I type CTRL+c when running outside gdb. When running gdb The "save as" button has the same effect (gray empty window) but it just waits there... And ctrl+c just closes it.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffddb91700 (LWP 15754)]
[New Thread 0x7fffdd390700 (LWP 15755)]
[New Thread 0x7fffd7fff700 (LWP 15756)]
[New Thread 0x7fffc8e09700 (LWP 15808)]
[New Thread 0x7fffc3fff700 (LWP 15809)]
[New Thread 0x7fffc37fe700 (LWP 15810)]
[New Thread 0x7fffc2ffd700 (LWP 15815)]
[New Thread 0x7fffc27fc700 (LWP 15816)]
[New Thread 0x7fffc1ffb700 (LWP 15817)]
[New Thread 0x7fffc17fa700 (LWP 15818)]
[New Thread 0x7fffc0ff9700 (LWP 15819)]
[New Thread 0x7fffa3fff700 (LWP 15820)]
[New Thread 0x7fff9bfff700 (LWP 15821)]
[New Thread 0x7fff9b7fe700 (LWP 15822)]
[New Thread 0x7fffa37fe700 (LWP 15823)]
[New Thread 0x7fffa2ffd700 (LWP 15824)]
[New Thread 0x7fff7f1e7700 (LWP 15831)]
[New Thread 0x7fff7a9e6700 (LWP 15832)]
[New Thread 0x7fff7e9e6700 (LWP 15833)]
[New Thread 0x7fff7e1e5700 (LWP 15834)]
[New Thread 0x7fff7d9e4700 (LWP 15835)]
[New Thread 0x7fff7d1e3700 (LWP 15836)]
[New Thread 0x7fff7c9e2700 (LWP 15837)]
[New Thread 0x7fff7c1e1700 (LWP 15838)]
[ INFO] [1366182158.957130007]: OpenGl version: 3.0 (GLSL 1.3).
[New Thread 0x7fff7a0e5700 (LWP 15851)]
[New Thread 0x7fff4e5de700 (LWP 15899)]
[New Thread 0x7fff4dddd700 (LWP 15904)]
[Thread 0x7fffd7fff700 (LWP 15756) exited]
[New Thread 0x7fffd7fff700 (LWP 15928)]
[New Thread 0x7fff44de9700 (LWP 15929)]
[Thread 0x7fffd7fff700 (LWP 15928) exited]
[Thread 0x7fff44de9700 (LWP 15929) exited]

and waits here

[fersarr]

After setting the ulimit to unlimited, when closing rqt with CTRL+c after the gray empty window I get the following

http://pastebin.com/kPzXHA1k

As you can probably tell, Im a noob using gdb and stack trackes... If you tell me exactly what commands to run, I will give them a try.

[dgossow]

This should be fixed with the next release of RViz. Thanks for reporting.