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
2005-01-12 03:55:33 +00:00
parent 9ed278d664
commit 42e66e22c7
1 changed files with 2 additions and 0 deletions
@@ -71,6 +71,8 @@ struct TMessengerInitPolicy : public ArrayTypeBase<BMessenger>
 	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