[SOLVED] Segmentation fault at exit of gui

[mlundh]

So it is not just me then..

It seems like they are on the bug report, i guess i should have posted one myself when i encountered the problem Lets hope someone finds a solution, I will probably spend some time on it, not sure when though...

[marcus]

There seems to be some issues with using SDL2/PySDL2 on Linux, but Windows and Mac OSX seems unaffected. There's a few issues that we have seen, but we missed the "Config device mapping" bug I've added an issue for it here and I've just pushed a workaround fix for it.

The others we found are:

• Opening OS dialogs crashes the application, there's a workaround for opening the Browse dialog for the bootloader
• Crashing when closing the application (issue)

All of these happen during calls to libraries, so the best we have been able to do right now is working around the issues. When we have more time we will investigate it more.

[marcus]

Just got my crazyflie 2 and running into a similar issue. I am running into this error when scanning for the crazyflie. The first time i opened the client it worked but then I compiled libusb manually and this issue started happening. The UI quits with the following being printed in the console:

2014-12-16 22:29:54.565 Python[600:6688] _createMenuRef called with existing principal MenuRef already associated with menu
2014-12-16 22:29:54.566 Python[600:6688] (
0 CoreFoundation 0x00007fff895eb64c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff868166de objc_exception_throw + 43
2 CoreFoundation 0x00007fff895eb4fd +[NSException raise:format:] + 205
3 AppKit 0x00007fff8722b315 -[NSCarbonMenuImpl _createMenuRef] + 62
4 AppKit 0x00007fff8722ac66 -[NSCarbonMenuImpl _instantiateCarbonMenu] + 139
5 AppKit 0x00007fff872294d2 -[NSApplication finishLaunching] + 947
6 AppKit 0x00007fff87228da1 -[NSApplication run] + 128
7 QtGui 0x000000010e005f18 _ZN19QEventDispatcherMac13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE + 1522
8 QtCore 0x000000010d4d56f1 _ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE + 77
9 QtCore 0x000000010d4d5870 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 370
10 QtCore 0x000000010d4d851f _ZN16QCoreApplication4execEv + 199
11 QtGui.so 0x000000010d7d4fca _ZL23meth_QApplication_exec_P7_objectS0_ + 80
12 Python 0x000000010c90962c PyEval_EvalFrameEx + 14394
13 Python 0x000000010c90c46a fast_function + 262
14 Python 0x000000010c909246 PyEval_EvalFrameEx + 13396
15 Python 0x000000010c905bbe PyEval_EvalCodeEx + 1409
16 Python 0x000000010c905637 PyEval_EvalCode + 54
17 Python 0x000000010c925926 run_mod + 53
18 Python 0x000000010c9259c9 PyRun_FileExFlags + 133
19 Python 0x000000010c925566 PyRun_SimpleFileExFlags + 769
20 Python 0x000000010c936c9b Py_Main + 3051
21 libdyld.dylib 0x00007fff82dca5c9 start + 1
)
Fatal Python error: (pygame parachute) Segmentation Fault
Abort trap: 6

This happen if I have the crazyradio 2 connected or disconnected. Any thoughts?

It seems that this is an old client since the pygame exception parachute is catching the exception. Could you update to the latest one? To get a better error message try bootloading the Crazyflie (menu Crazyflie->Bootloader and Initiate cold boot). The error is probably caused by permission issues when opening the Crazyradio USB device. For fixing this have a look at adding the UDEV rules we use in the Bitcraze VM (info here).

[Malte]

i´ve tried the workaround and it´s working.

[mighty_falcon]

Just got my crazyflie 2 and running into a similar issue. I am running into this error when scanning for the crazyflie. The first time i opened the client it worked but then I compiled libusb manually and this issue started happening. The UI quits with the following being printed in the console:

2014-12-16 22:29:54.565 Python[600:6688] _createMenuRef called with existing principal MenuRef already associated with menu
2014-12-16 22:29:54.566 Python[600:6688] (
0 CoreFoundation 0x00007fff895eb64c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff868166de objc_exception_throw + 43
2 CoreFoundation 0x00007fff895eb4fd +[NSException raise:format:] + 205
3 AppKit 0x00007fff8722b315 -[NSCarbonMenuImpl _createMenuRef] + 62
4 AppKit 0x00007fff8722ac66 -[NSCarbonMenuImpl _instantiateCarbonMenu] + 139
5 AppKit 0x00007fff872294d2 -[NSApplication finishLaunching] + 947
6 AppKit 0x00007fff87228da1 -[NSApplication run] + 128
7 QtGui 0x000000010e005f18 _ZN19QEventDispatcherMac13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE + 1522
8 QtCore 0x000000010d4d56f1 _ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE + 77
9 QtCore 0x000000010d4d5870 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 370
10 QtCore 0x000000010d4d851f _ZN16QCoreApplication4execEv + 199
11 QtGui.so 0x000000010d7d4fca _ZL23meth_QApplication_exec_P7_objectS0_ + 80
12 Python 0x000000010c90962c PyEval_EvalFrameEx + 14394
13 Python 0x000000010c90c46a fast_function + 262
14 Python 0x000000010c909246 PyEval_EvalFrameEx + 13396
15 Python 0x000000010c905bbe PyEval_EvalCodeEx + 1409
16 Python 0x000000010c905637 PyEval_EvalCode + 54
17 Python 0x000000010c925926 run_mod + 53
18 Python 0x000000010c9259c9 PyRun_FileExFlags + 133
19 Python 0x000000010c925566 PyRun_SimpleFileExFlags + 769
20 Python 0x000000010c936c9b Py_Main + 3051
21 libdyld.dylib 0x00007fff82dca5c9 start + 1
)
Fatal Python error: (pygame parachute) Segmentation Fault
Abort trap: 6

This happen if I have the crazyradio 2 connected or disconnected. Any thoughts?

It seems that this is an old client since the pygame exception parachute is catching the exception. Could you update to the latest one? To get a better error message try bootloading the Crazyflie (menu Crazyflie->Bootloader and Initiate cold boot). The error is probably caused by permission issues when opening the Crazyradio USB device. For fixing this have a look at adding the UDEV rules we use in the Bitcraze VM (info here).

Yes it was an old client I had first cloned the repo from bitbucket, then realized it had moved over to github. Should of known something was up since the last commit in the bitbucket repo was from 2013

[marcus]

The latest version in the repository on master should fix this error (among others). SDL2 is not used on Linux anymore, the devices are accessed directly by /dev/input/js*. If you feel up for it then pull the latest version and try it out, if you find any issues let me know.

[Malte]

for me the newest version dosen´t work at all:

INFO:cfclient.cfclient:Disabling STL printouts
INFO:cfclient.utils.config:Dist config read from /usr/cfclient/configs/config.json
INFO:cfclient.utils.config:Config file read from [/root/.local/cfclient/config.json]
===== 2014.12.22 09:12:01 =====
Traceback (most recent call last):
File "/usr/bin/cfclient", line 105, in <module>
cfclient.main()
File "/usr/lib/python2.7/site-packages/cfclient/cfclient.py", line 135, in main
main_window = MainUI()
File "/usr/lib/python2.7/site-packages/cfclient/ui/main.py", line 114, in __init__
self.joystickReader = JoystickReader()
File "/usr/lib/python2.7/site-packages/cfclient/utils/input.py", line 72, in __init__
from cfclient.utils.joystick.linuxjsdev import Joystick
ImportError: No module named joystick.linuxjsdev
QThread: Destroyed while thread is still running

For now i checkt the old (2d2ce86a69. . .) out and using this version.

[dbrgn]

Happened to me too when installing via setup.py. I think there's a package definition missing in there, as it works when starting locally from source.

[tobias]

There are some new commit to the client now that hopefully fixes the linux problems.

[dbrgn]

There are some new commit to the client now that hopefully fixes the linux problems.

Shouldn't `cfclient.utils.joystick` be added to the setup.py `packages` argument to fix the error reported above?