OSX Crash at Exit

[Frank]

I was wondering whether something fishy might be going on at Exit.
When Qt is shutting down, i see the exception more often than not, I
was wondering whether there is anything that can be done about it.
There seems no way of debugging what is actually going on ...

thanks in advance
Frank


Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000004813d10
Crashed Thread: 0

Thread 0 Crashed:
0 ??? 0x04813d10 0 + 75578640
1 libqtjambi.jnilib 0x04a8a0f6
QtJambiLinkUserData::~QtJambiLinkUserData() + 44
2 libQtCore.4.dylib 0x0494d09e void
qDeleteAll<QObjectUserData* const*>(QObjectUserData* const*,
QObjectUserData* const*) + 46
3 libQtCore.4.dylib 0x04948ba5
QObjectPrivate::~QObjectPrivate() + 69
4 libQtCore.4.dylib 0x0494bd23 QObject::~QObject() +
1235
5 libQtGui.4.dylib 0x04cc472c QPMCache::~QPMCache() +
236
6 libQtGui.4.dylib 0x04cc37a1 __tcf_0 + 33
7 libSystem.B.dylib 0x92353cfc __cxa_finalize + 241
8 libSystem.B.dylib 0x92353bf0 exit + 33
9 mono 0x0006ca76
ves_icall_System_Environment_GetGacPath + 0 (icall.c:6621)
10 ??? 0x1aa141bf 0 + 446775743
11 ??? 0x008d03ed 0 + 9241581
12 ??? 0x008d0203 0 + 9241091
13 mono 0x000aa538 mono_runtime_exec_main +
249 (object.c:3310)
14 mono 0x000ae58b mono_runtime_run_main +
340 (object.c:3089)
15 mono 0x00004cc2 mono_main + 5751
(driver.c:969)

[david...@gmail.com]

How are you exiting your app? I haven't had this problem before. Try
the new 4.5.0 version.

Thanks,

David.

[Frank Bergmann]

At first i just let the application end after qapplication.exec, then
i tried calling Environment.Exit, and now finally get to quit it using
mono-posix.

Thanks for getting the new 4.5.0 version out, it works fine after
upgrading mono. As for the problem with the shutdown the only
possibility I saw was to use some mono-posix functions to ensure that
the application definitely quits when needed to. However the clean
solution would probably be to provide some way in qtjambi (perhaps
when calling QApplication::initialize) to register a shutdown /
terminate handler that would catch those signals.

Anyway ... that crash at exit is no longer a show stopper for me
best
Frank