Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Parent Lock does not remove on exit version 25

  • 4 件の返信
  • 4 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: cdorlandi

more options

With the newest update, Version 25, the Parent.Lock file does not delete during Firefox exit. This problem has never happened before. I am using Windows 7 Home 64 bit on a Gateway SX2800. When Parent.Lock is removed, Firefox will open normally but if closed, it will error that it is still running if you try to open another session (and no, it is not running in Task Manager) . Log out, log back in, remove Parent.Lock. Firefox works again. Seems we need a fix to Version 25 already.

With the newest update, Version 25, the Parent.Lock file does not delete during Firefox exit. This problem has never happened before. I am using Windows 7 Home 64 bit on a Gateway SX2800. When Parent.Lock is removed, Firefox will open normally but if closed, it will error that it is still running if you try to open another session (and no, it is not running in Task Manager) . Log out, log back in, remove Parent.Lock. Firefox works again. Seems we need a fix to Version 25 already.

選ばれた解決策

The presence of a parent.lock file shouldn't prevent Firefox from starting.
Firefox uses the time stamp of this file and compare it with the toolkit.startup.last_success pref to check for startup issues (Bug 294260).

You can check for problems with preferences.
Rename or delete the prefs.js file and possible numbered prefs-##.js and user.js files to reset all prefs to the default value.

この回答をすべて読む 👍 0

すべての返信 (4)

more options

Hi,

Please try creating a new profile and then removing the last one. Instructions on how to do this are located in the Profile Manager - Create, remove or switch Firefox profiles article.

Hope this helps!

Curtis

more options

選ばれた解決策

The presence of a parent.lock file shouldn't prevent Firefox from starting.
Firefox uses the time stamp of this file and compare it with the toolkit.startup.last_success pref to check for startup issues (Bug 294260).

You can check for problems with preferences.
Rename or delete the prefs.js file and possible numbered prefs-##.js and user.js files to reset all prefs to the default value.

more options

Deleted the prefs.js file and the problem went away. Of course, everything (home page, add-ons, etc.) reloaded, but that was probably for the best. Seems to be working fine except for the tab location. Will check other postings for that.

more options

Didn't want to create a new profile, and another answer proved to help. Thanks for the response.