Project: SWT
Bug 294368 Mozilla SWT Browser AppFileLocProvider has caching issues
Reported: 2009-11-05 13:58:32 | Status: resolved fixed

The AppFileLocProvider changes it's answer for the location of "ProfD" part way through the initialization and this is really messing with the caching done in the nsDirectoryService. It looks like what's happening is the nsDirectoryService is remembering the <empty> value and not going back to the provider to check for it again. We need to signal the need to refresh the cache by perhaps re-registering the provider or else explicitly set the property (or else come up with something even better).

Files changed in fix:
bundles/org.eclipse.swt/Eclipse SWT Mozilla/carbon/org/eclipse/swt/browser/MozillaDelegate.java bundles/org.eclipse.swt/Eclipse SWT Mozilla/cocoa/org/eclipse/swt/browser/MozillaDelegate.java bundles/org.eclipse.swt/Eclipse SWT Mozilla/common/org/eclipse/swt/browser/AppFileLocProvider.java bundles/org.eclipse.swt/Eclipse SWT Mozilla/common/org/eclipse/swt/browser/Mozilla.java bundles/org.eclipse.swt/Eclipse SWT Mozilla/gtk/org/eclipse/swt/browser/MozillaDelegate.java bundles/org.eclipse.swt/Eclipse SWT Mozilla/motif/org/eclipse/swt/browser/MozillaDelegate.java bundles/org.eclipse.swt/Eclipse SWT Mozilla/win32/org/eclipse/swt/browser/MozillaDelegate.java bundles/org.eclipse.swt/Eclipse SWT PI/win32/org/eclipse/swt/internal/win32/OS.java