X
Tippen Sie hierhin, um die Version dieser Website für Mobilgeräte aufzurufen.

Hilfeforum

Firefox 29.0.1 leaves process running after exit, which must be terminated manually before Firefox will re-start.

Veröffentlicht

After updating to Firefox 29.0, firefox.exe *32 process keeps running after application exit, and must be terminated manually before Firefox will re-start. The update to 29.0.1 did not solve the issue. All updates prior to 29.0 never exhibited this problem, and there have been no other changes to my system, so this issue originated with 29.0.

After updating to Firefox 29.0, firefox.exe *32 process keeps running after application exit, and must be terminated manually before Firefox will re-start. The update to 29.0.1 did not solve the issue. All updates prior to 29.0 never exhibited this problem, and there have been no other changes to my system, so this issue originated with 29.0.

Mehr Details zum System

Installierte Plugins

  • Google Update
  • Next Generation Java Plug-in 10.55.2 for Mozilla browsers
  • 5.1.30214.0
  • Adobe PDF Plug-In For Firefox and Netscape 11.0.06
  • Adobe PDF Plug-In For Firefox and Netscape 10.1.9
  • Shockwave Flash 11.9 r900
  • GEPlugin
  • iTunes Detector Plug-in
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Citrix Online App Detector Plugin
  • NPWLPG
  • The plug-in allows you to open and edit files using Microsoft Office applications
  • Office Authorization plug-in for NPAPI browsers

Anwendung

  • Firefox 29.0.1
  • User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0
  • Hilfe-URL: https://support.mozilla.org/1/firefox/29.0.1/WINNT/en-US/

Erweiterungen

  • Troubleshooter 1.1a (troubleshooter@mozilla.org)
  • Adobe Acrobat - Create PDF 1.2 (web2pdfextension@web2pdf.adobedotcom) (inaktiv)
  • Norton Toolbar 2014.7.1.1 ({2D3F3651-74B9-4795-BDEC-6DA2F431CB62}) (inaktiv)
  • Norton Vulnerability Protection 12.2.0.5 - 1 ({BBDA0591-3099-440a-AA10-41764D9DB4DB}) (inaktiv)

JavaScript

  • incrementalGCEnabled: True

Grafiken

  • adapterDescription: AMD Radeon HD 6800 Series
  • adapterDescription2:
  • adapterDeviceID: 0x6738
  • adapterDeviceID2:
  • adapterDrivers: aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
  • adapterDrivers2:
  • adapterRAM: 1024
  • adapterRAM2:
  • adapterVendorID: 0x1002
  • adapterVendorID2:
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 6.2.9200.16571
  • driverDate: 4-19-2011
  • driverDate2:
  • driverVersion: 8.850.0.0
  • driverVersion2:
  • info: {u'AzureCanvasBackend': u'direct2d', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'direct2d', u'AzureSkiaAccelerated': 0}
  • isGPU2Active: False
  • numAcceleratedWindows: 1
  • numTotalWindows: 1
  • webglRenderer: Google Inc. -- ANGLE (AMD Radeon HD 6800 Series Direct3D9Ex vs_3_0 ps_3_0)
  • windowLayerManagerRemote: False
  • windowLayerManagerType: Direct3D 10

Veränderte Einstellungen

  • accessibility.typeaheadfind.flashBar: 0
  • browser.cache.disk.capacity: 358400
  • browser.cache.disk.smart_size.first_run: False
  • browser.cache.disk.smart_size.use_old_max: False
  • browser.cache.disk.smart_size_cached_value: 358400
  • browser.display.background_color: #C0C0C0
  • browser.display.use_system_colors: True
  • browser.places.smartBookmarksVersion: 6
  • browser.sessionstore.upgradeBackup.latestBuildID: 20140506152807
  • browser.startup.homepage: about:blank
  • browser.startup.homepage_override.buildID: 20140506152807
  • browser.startup.homepage_override.mstone: 29.0.1
  • browser.tabs.loadInBackground: False
  • dom.mozApps.used: True
  • dom.w3c_touch_events.expose: False
  • extensions.lastAppVersion: 29.0.1
  • font.internaluseonly.changed: True
  • gfx.direct3d.last_used_feature_level_idx: 0
  • gfx.direct3d.prefer_10_1: True
  • network.cookie.prefsMigrated: True
  • places.database.lastMaintenance: 1399844134
  • places.history.enabled: False
  • places.history.expiration.transient_current_max_pages: 104858
  • places.history.expiration.transient_optimal_database_size: 167772160
  • plugin.disable_full_page_plugin_for_types: application/pdf
  • plugin.importedState: True
  • plugin.state.npdeployjava: 0
  • plugin.state.nppdf: 2
  • privacy.clearOnShutdown.cookies: False
  • privacy.clearOnShutdown.formdata: False
  • privacy.sanitize.migrateFx3Prefs: True
  • privacy.sanitize.sanitizeOnShutdown: True
  • security.warn_viewing_mixed: False
  • storage.vacuum.last.index: 1
  • storage.vacuum.last.places.sqlite: 1398308215

Verschiedenes

  • User JS: Nein
  • Barrierefreiheit: Nein
guigs 1072 Lösungen 11697 Antworten
Veröffentlicht

Hi xignt, It is quite possible that you are being affected by having clear history on shutdown checked.

  • [Bug 1005958 - Disable seer until new backend is rewritten ]
  • [Bug 965309 - Worker hang at shutdown with XHR]

This will be alleviated as they work on a patch for this issue. However they are looking for a regression window on this issue and you can check it out in the second bug. What is the options selected for history? 'remember history'?

Hi xignt, It is quite possible that you are being affected by having clear history on shutdown checked. *[Bug 1005958 - Disable seer until new backend is rewritten ] *[Bug 965309 - Worker hang at shutdown with XHR] This will be alleviated as they work on a patch for this issue. However they are looking for a regression window on this issue and you can check it out in the second bug. What is the options selected for history? 'remember history'?
John99 971 Lösungen 13138 Antworten
Veröffentlicht

Looks like at present #c14 they are not too interested in a specific regression range.

Does Firefox work ok if you do not set Firefox to clear History on closedown ?
If so it probably is an effect of the above mentioned known bugs.

I imagine Firefox will still be able to run a Private Browsing Window without problems, but you may need to close that before exiting from Firefox.

(One of several related threads is firefox already running when trying to open Firefox /questions/1001267#answer-577670 )

Looks like at present <sup>[https://bugzilla.mozilla.org/show_bug.cgi?id=965309#c14 #c14]</sup> they are not too interested in a specific regression range. Does Firefox work ok if you do not set Firefox to clear History on closedown ? <br /> If so it probably is an effect of the above mentioned known bugs. I imagine Firefox will still be able to run a Private Browsing Window without problems, but you may need to close that before exiting from Firefox. (One of several related threads is ''firefox already running when trying to open Firefox'' [/questions/1001267#answer-577670] )
FredMcD
  • Top 10 Contributor
4248 Lösungen 59425 Antworten
Veröffentlicht

https://support.mozilla.org/questions/997866?esab=a&s=&r=1&as=s
This is not a cure but will make it easier if Firefox locks up.

'''https://support.mozilla.org/questions/997866?esab=a&s=&r=1&as=s'''<BR> This is not a cure but will make it easier if Firefox locks up.
Veröffentlicht

Hilfreiche Antwort

Thank you, I did have my history set to not remember browsing history, and to clear cache and browsing/download history on exit. After temporarily re-enabling those history items, exiting, restarting and visiting a web site, exiting again, and re-disabling those history items, further startups/exits worked fine without leaving a process running. So that seems to be the work-around "fix" until the underlying bug(s) are addressed.

Thank you, I did have my history set to not remember browsing history, and to clear cache and browsing/download history on exit. After temporarily re-enabling those history items, exiting, restarting and visiting a web site, exiting again, and re-disabling those history items, further startups/exits worked fine without leaving a process running. So that seems to be the work-around "fix" until the underlying bug(s) are addressed.
John99 971 Lösungen 13138 Antworten
Veröffentlicht

Glad to hear that helps.

It appears this or related bugs affected other versions also, but depends partly on the Firefox configuration. The main factor being the clearing of History when Firefox closes down.

I guess that most users do not set Firefox to clear History, after all it takes away the the handy feature of the location bar being able to predict addresses based on History & the ability to look at your history. It is something I would have hoped Telemetry would have picked up and so alerted engineers, but maybe those users clearing History are not enabling telemetry.

That feature was IIRC introduced after developers missed a Firefox 4 memory usage issue.

Glad to hear that helps. It appears this or related bugs affected other versions also, but depends partly on the Firefox configuration. The main factor being the clearing of History when Firefox closes down. I guess that most users do not set Firefox to clear History, after all it takes away the the handy feature of the location bar being able to predict addresses based on History & the ability to look at your history. It is something I would have hoped Telemetry would have picked up and so alerted engineers, but maybe those users clearing History are not enabling telemetry. * [[Send performance data to Mozilla to help improve Firefox]] That feature was IIRC introduced after developers missed a Firefox 4 memory usage issue.
Veröffentlicht

Hilfreiche Antwort

Learned a couple more things:

1. The first fix didn't stick after the next power cycle. Still have the problem while history items are disabled.

2. Telemetry actually appears to be part of the issue. Even with history automatically cleared/disabled, enabling telemetry by itself clears the problem, and disabling it brings the problem back.

Go figure. Hope this is helping someone with their detective work....

Learned a couple more things: 1. The first fix didn't stick after the next power cycle. Still have the problem while history items are disabled. 2. Telemetry actually appears to be part of the issue. Even with history automatically cleared/disabled, enabling telemetry by itself clears the problem, and disabling it brings the problem back. Go figure. Hope this is helping someone with their detective work....

Geändert am von xignt

John99 971 Lösungen 13138 Antworten
Veröffentlicht

Hi xignt,
Thanks for the update.

Sounds like a good reason to turn on telemetry.

;-)

Mixed and unexpected results then. This problem has proved rather difficult to reproduce reliably and only affects some people. Problems that affect everyone or are easy to demonstrate and reproduce tend to be easier to investigate and fix.

I am no expert on the closedown problems. One of the bugs does mention the process is rather fragile. Presumably problems may be affected by many things that are involved with the close down procedure.

I guess you have demonstrated that telemetry is one of those processes. Interestingly if telemetry use actually helps and prevents the hang that may be distorting the view of developers when looking at the telemetry results. I wonder if this could make the problem appear less severe.

If I understand correctly you are now reporting that

  1. Setting Firefox to remember History does help whilst the computer is powered up and Firefox is closed and reopened repeatedly with success.
  2. Once Firefox is closed down and then the System closed down and powered off the problem reappears.
  • Have you looked at the settings ?
    Does the preferences display indicate the setting has changed after powering on.
    Is Firefox again then set to something other than Remember History.

I suspect we will need to wait for the fixes to the known bugs to work there way through before doing any serious troubleshooting on this issue.

Hi xignt, <br /> Thanks for the update. Sounds like a good reason to turn on telemetry. ===;-)=== Mixed and unexpected results then. This problem has proved rather difficult to reproduce reliably and only affects some people. Problems that affect everyone or are easy to demonstrate and reproduce tend to be easier to investigate and fix. I am no expert on the closedown problems. One of the bugs does mention the process is rather fragile. Presumably problems may be affected by many things that are involved with the close down procedure. I guess you have demonstrated that telemetry is one of those processes. Interestingly if telemetry use actually helps and prevents the hang that may be distorting the view of developers when looking at the telemetry results. I wonder if this could make the problem appear less severe. If I understand correctly you are now reporting that # Setting Firefox to remember History does help whilst the computer is powered up and Firefox is closed and reopened repeatedly with success. # Once Firefox is closed down and then the System closed down and powered off the problem reappears. * Have you looked at the settings ? <br /> Does the preferences display indicate the setting has changed after powering on. <br /> Is Firefox again then set to something other than Remember History. I suspect we will need to wait for the fixes to the known bugs to work there way through before doing any serious troubleshooting on this issue.
Veröffentlicht

Fragesteller

Thanks for the response, and you are right, for now the only one being helped by leaving telemetry on is me, because there is (apparently) no problem to report when it is on.

Slight clarification:

1. Enabling history and cache fixes problem.

2. Enabling telemetry fixes problem.

3. Enabling history and cache, cycling FireFox on/off, then disabling history and cache, fixes problem during current power cycle, but not persistently between power cycles.

4. All the above settings do persist across power cycles.

Thanks for the response, and you are right, for now the only one being helped by leaving telemetry on is me, because there is (apparently) no problem to report when it is on. Slight clarification: 1. Enabling history and cache fixes problem. 2. Enabling telemetry fixes problem. 3. Enabling history and cache, cycling FireFox on/off, then disabling history and cache, fixes problem during current power cycle, but not persistently between power cycles. 4. All the above settings do persist across power cycles.
John99 971 Lösungen 13138 Antworten
Veröffentlicht

Thanks for the clarification.

Telemetry report startup and other performance related data it is always useful to developers to have telemetry enabled. Note aggregated annonymised results are available

  • see the interactive results at http://telemetry.mozilla.org
  • Your own results stored on & from your own computer
    • If FHR is on, & has been running a while. (Still rather limited it is Work In Progress) about:healthreport
      see Firefox Health Report - understand your browser performance
    • Again assuming it is enabled and has been for a while about:telemetry
      The first one
      Slow SQL Statements
      could be of interest,
      and with problems on the original Fx29.0 may well have picked up issues with netpredictions.sqlite whilst that was enabled
Thanks for the clarification. Telemetry report startup and other performance related data it is always useful to developers to have telemetry enabled. Note aggregated annonymised results are available * see the interactive results at http://telemetry.mozilla.org * Your own results ''' stored on''' & from your own computer ** If FHR is on, & has been running a while. (Still rather limited it is Work In Progress) ''about:healthreport'' <br /> see [[Firefox Health Report - understand your browser performance]] ** Again assuming it is enabled and has been for a while ''about:telemetry''<br /> The first one <br />Slow SQL Statements <br /> could be of interest, <br /> and with problems on the original Fx29.0 may well have picked up issues with ''netpredictions.sqlite'' whilst that was enabled
John99 971 Lösungen 13138 Antworten
Veröffentlicht

UPDATE

Note one potential fix is now in the very recent Firefox Beta 30b8 Initial reports suggest this fixes the issue. (Bug1005487#c38) If you have been suffering from this problem and want a fix now instead of in a few weeks time you may wish to download and install the Beta version of Firefox.

The beta version is effectively a release candidate but is only intended for advanced users or testers. I would be interested to hear feedback from those of you that do test this out.

Beta version download

UPDATE Note one potential fix is now in the very recent Firefox Beta 30b8 Initial reports suggest this fixes the issue. <sup>(Bug1005487#c38)</sup> If you have been suffering from this problem and want a fix now instead of in a few weeks time you may wish to download and install the Beta version of Firefox. The beta version is effectively a release candidate but is only intended for advanced users or testers. I would be interested to hear feedback from those of you that do test this out. Beta version download * http://www.mozilla.org/en-US/firefox/channel/#beta/beta-desktop