QA/Firefox3/Investigation/Norton 360: Difference between revisions
| Line 10: | Line 10: | ||
= Investigation = | = Investigation = | ||
''Tomcat | The issue can be reliably reproduced if you are running: Firefox 3, Norton 360, and have the Cooliris add-on installed. Using this mechanism we've been able to determine: | ||
* firefox.exe is being held open by appMan32.dll which is itself being affected by coffplgn.dll | |||
* unclear why the profile isn't remaining locked while firefox.exe remains open | |||
* mfinkle suspected jemalloc based on a stack obtained by Tomcat | |||
* jemalloc-free builds show that firefox.exe remains open, but the SQL files do *not* stay locked | |||
Revision as of 14:44, 17 September 2008
Summary
Some users running Norton 360 v2 and Norton Internet Security 2008.5 have reported that after upgrading to Firefox 3, they can no longer access their bookmarks, create new bookmarks, create or use browser history, or access their saved passwords from IdentitySafe.
The issue appears to be caused by firefox.exe not exiting properly and locking the new SQL files used to store this information. If a user starts Firefox after a reboot, they will be able to see their bookmarks and history; as soon as they exit and relaunch Firefox, though, the problem re-appears.
Workarounds
Two workarounds are known to exist:
- Using Task Manager, kill all firefox.exe processes
- Remove coffplgn.dll from C:\Program Files\Mozilla Firefox\Components
Investigation
The issue can be reliably reproduced if you are running: Firefox 3, Norton 360, and have the Cooliris add-on installed. Using this mechanism we've been able to determine:
- firefox.exe is being held open by appMan32.dll which is itself being affected by coffplgn.dll
- unclear why the profile isn't remaining locked while firefox.exe remains open
- mfinkle suspected jemalloc based on a stack obtained by Tomcat
- jemalloc-free builds show that firefox.exe remains open, but the SQL files do *not* stay locked