SingletonHolder destructor is called very late

Bug #661367 reported by Maciej Muehleisen on 2010-10-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openWNS Library

Bug Description

The method destroySingleton() is registered using std::atexit and therefore called very late. Most likely the whole simulator core is already destroyed.

If for example the Singleton drives from PeriodicTimeout the program will exit with Segfault since the PeriodicTimeout Destructor cannot cancel its last event since the EventScheduler is already destroyed. We should assure Singletons are destroyed before the core is.

Do we have a Signal for that? Can we register the Singleton to use that signal?

Changed in openwns-library:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers