Community
Participate
Working Groups
I've found that ComposedAdapterFactory instantiated in many places, but not disposed later. It may result in item provider leaks. May be it would be nice to create one global instance of ComposedAdapterFactory, and use it everywhere.
Thank you for pointing this out, we had this problem before, it still seems to be present!
added ComposedAdapterFactory.dispose() where needed!
approved
More issues: org.eclipse.emf.emfstore.client.ui.dialogs.login.ServerInfoSelectionDialog:109 org.eclipse.emf.emfstore.client.ui.dialogs.merge.util.DecisionUtil:35 org.eclipse.emf.emfstore.client.ui.views.emfstorebrowser.dialogs.admin.PropertiesComposite:477 org.eclipse.emf.emfstore.client.ui.views.emfstorebrowser.provider.ESBrowserContentProvider:33 org.eclipse.emf.emfstore.client.ui.views.emfstorebrowser.provider.ESBrowserLabelProvider:32 org.eclipse.emf.emfstore.client.ui.views.historybrowserview.HistoryTableContentProvider:31 org.eclipse.emf.emfstore.client.ui.views.historybrowserview.HistoryTableLabelProvider:36 All credits goes to JDT's Java Search :)
I've moved the instantiation of the ComposedAdapterFactory into the Activator of the the client.ui plugin. The factory is disposed upon Activator#stop. Note that DecisionUtil did not own a ComposedAdapterFactory anymore and the HistoryTableContentProvider and HistoryTableLabelProvider classes have been removed, all other occurences of ComposedAdapterFactorys thus have been replaced with a getter.