Closed Bug 270446 Opened 21 years ago Closed 21 years ago

Event 1517 in Windows XP Application log after running Firefox

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: david.rice, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 After installing Firefox 1.0 on 3 different computers I get this error in the Application log any time I shut down or restart after running Firefox. If I don't run Firefox during the session I don't get the error. All machines are WinXP Service Pack 2. Two are domain members and the other is a standalone. No services are running as a local user account. I am logging in as a user with full administrative privileges. I never got this error before installing Firefox and I tested it several times to verify that it was connected with running Firefox before I reported it. It may be minor but it makes me wonder if it could be connected with other problems or if it might indicate that some handles are not being released. Even if it is harmless it would be nice to fix it so it doesn't clutter the event log. (begin event text) Event Type: Warning Event Source: Userenv Event Category: None Event ID: 1517 Date: 11/16/2004 Time: 9:55:25 AM User: NT AUTHORITY\SYSTEM Computer: [computer name] Description: Windows saved user [domain]\[username] registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. (end event text) Reproducible: Always Steps to Reproduce: 1. Log in with local administrator privileges (i.e., this is not a permission or usr rights issue) 2. Install Firefox on Windows XP Service Pack 2 (not tested on SP1) 3. Run Firefox while logged in as administrator 4. Exit Firefox 5. Check Task Manager and verify that firefox.exe is not still running 6. Restart computer 7. Check Application log 8. See Event 1517 Actual Results: Event 1517 present in event log as shown in details. Expected Results: Should have released registry so that event did not occur. I verified the issue on 3 computers before sending in a bug report.
Are you sure FF is completely unloaded from memory? Was Sun Java started? http://www.eventid.net/display.asp?eventid=1517&source=
(In reply to comment #1) > Are you sure FF is completely unloaded from memory? Was Sun Java started? > http://www.eventid.net/display.asp?eventid=1517&source= I was too tired when I was troubleshooting before. This actually occurs on EVERY reboot even if Firefox is not run and even after Firefox is uninstalled. I can trace the error on all 3 computers back to the date and time I installed Firefox. Once Firefox is installed and run, this event appears on every restart and I can't find any way to make it go away. I removed FF and Sun Java from one computer and went back to IE and it still happens. Does FF install some service for the Talkback feature or other service that is not removed by the uninstall? I am a little worried because even uninstalling Firefox doesn't make this event go away.
I think this is caused by the DcomLaunch service not releasing the HKCU registry hive during logoff. Does Firefox install something related to COM+ or DCOM that might cause this? I know the installer says something about Cross-Platform COM+ during the install. See this post for more info on how I got to this point: http://forums.mozillazine.org/viewtopic.php?t=165096
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Does not occur after a full format and reload. Not sure why it started right after FireFox install on 3 computers but reloading fixed it on 1 of them so it must not be a fully reproducible bug if it is even a bug at all.
You need to log in before you can comment on or make changes to this bug.