Community
Participate
Working Groups
Build Identifier: if something happens like bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=359294 then the persistent saving of framework state seems to be disabled. This leads to very strange behavior: bundles that were supposedly uninstalled are actually still alive and in the framework after restart, despite being uninstalled. (i.e. no apparent failure indicating that uninstall failed.. ) This is based on a post-mortem with Tom... Reproducible: Didn't try
We should be more protective in the state saver thread to make sure that all state saving is disabled on runtime exception during one save.
Upon further review I am not sure what improvements we need to make here. Erin, I assume you always ensure the framework is shutdown? That should force the .bundledata to be written with the very latest information even if an exception is thrown while writing the .state .lazy. So far I have not figured out how to reproduce the strange behavior you describe.
Returning as works for me. I was unable to reproduce the issue.