Simon Hausmann 7c029e83a3 Fix invalid memory read when shutting down QML applications ... As the last line in the QObject destructor, we call setParentHelper(0) to remove ourselves from the parent. In the process of that we also initiate the QML parentChanged callback. The first thing that parentChanged callback used to do (but now does it too late, after 26350b5ceafa0ade1328037f6234a7d288eb8f48 in qtdeclarative) is to check if the object was deleted and then return. We could re-introduce the check there, but I think it's cleaner to not bother calling the callback on a dead object in the first place. Change-Id: Ia4d43b65a9b3744a451b4c312a2d6f9c0e3b67dc Reviewed-by: Lars Knoll <lars.knoll@digia.com>		2013-11-29 09:54:47 +01:00
..
signalbug	tests: Make the QT assignments more explicit	2013-08-21 19:05:52 +02:00
test	Set the Qt API level to compatibility mode in all tests.	2012-08-01 15:37:46 +02:00
.gitignore	QObject-test: Reorganize subprocess.	2011-12-14 07:07:09 +01:00
qobject.pro	Fixed tst_qobject signalbug silently not compiled in -fast builds.	2012-02-23 09:06:44 +01:00
tst_qobject.cpp	Fix invalid memory read when shutting down QML applications	2013-11-29 09:54:47 +01:00