搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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.