From 42e66e22c7ba2f73c0252c81d71cf906a7d75e24 Mon Sep 17 00:00:00 2001 From: Ingo Weinhold Date: Wed, 12 Jan 2005 03:55:33 +0000 Subject: [PATCH] Really, a static BLooper attribute is not exactly a brilliant choice. Now every time the App Kit test add-on is loaded a BLooper is constructed. And it seems we somehow leak those loopers, since when some test actually starts, already six or seven looper threads do exist. Added only a comment, since I didn't dare to meddle with those templated BMessage unit tests. git-svn-id: file:///srv/svn/repos/haiku/trunk/current@10688 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- src/tests/kits/app/bmessage/MessageMessengerItemTest.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/tests/kits/app/bmessage/MessageMessengerItemTest.h b/src/tests/kits/app/bmessage/MessageMessengerItemTest.h index 574ea6b742..d3d05d20bb 100644 --- a/src/tests/kits/app/bmessage/MessageMessengerItemTest.h +++ b/src/tests/kits/app/bmessage/MessageMessengerItemTest.h @@ -71,6 +71,8 @@ struct TMessengerInitPolicy : public ArrayTypeBase private: static BLooper sLooper; }; +// bonefish: TODO: Sorry, but this sucks. Just loading the App Kit test add-on +// will already create a BLooper. BLooper TMessengerInitPolicy::sLooper; struct TMessengerAssertPolicy