Anton Kreuzkamp

Hi, thanks for reporting the issue. All I can tell from this, is that this seems to be related to library-paths and environment variables. Did you compile GammaRay with `-DGAMMARAY_INSTALL_QT_LAYOUT=true`...

Ok, from all I can tell this is basically a regression in Qt, because at qtquickwindow.cpp:551 they don't check `renderer` for nullness... I intercepted it from the debugger and returned...

gammaray includes the two unittests `probeabitest` and `probeabidetectortest`. Could you please run them and tell us, if they work fine? Then, the output of `ldd path/To/Your/Applications/Executable` (ideally cropped to qt-related...

Ah, and then there is a `--probe ` commandline option you can use to override the automatic ABI detection. Use `gammaray --list-probes` to get a list of all ABIs you...

Option 3) A mix of both: We could try to rebuild Qt's pointer classes in js, especially QPointer and QWeakPointer. - QPointer is a pointer that resets itself as soon...

To clarify: One of the concerns of this issue is to ask you, how to properly do memory management in JavaScript ;)

Thanks for your reply, @labsin. I know the general concept of garbage collecting, though. The idea behind gc is, that you don't need to take care of memory management. But...

We maintain lot's of references to items at random locations, but still we want to explicitly delete objects. The gc won't clean up anything, if we don't remove all references,...

I'm not mainly arguing about memory usage. In C++ having a dangling reference will crash, in JS having a dangling reference will simply produce undefined behavior. That's what I'm arguing....

@ChALkeR With "dangling reference" I mean a reference to an object, that is supposed to be deleted. e.g. ``` qml FocusScope { id: fs property Item fi Repeater { id:...