为提升您的使用体验，本站正在维护，部分功能暂时无法使用。如果本站文章无法解决您的问题，您想要向社区提问的话，请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问，我们的支持社区将会很快回复您的疑问。

Avatar for Username

搜索 | 用户支持

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

详细了解

话题已存档。 如果需要帮助请提出新问题。

console shows kernal error during startup

  • 1 个回答
  • 2 人有此问题
  • 1 次查看
  • 最后回复者为 guigs

VerizonSucks
VerizonSucks
more options

7/8/14 2:06:55 AM kernel Data/Stack execution not permitted: firefox[pid 177] at virtual address 0x116599000, protections were read-write

I get this sort of error ALL THE TIME but noticed it now when just starting Firefox.


7/8/14 2:06:52 AM [0x0-0x1a01a].org.mozilla.firefox[177] Background starting...

7/8/14 2:06:55 AM kernel Data/Stack execution not permitted: firefox[pid 177] at virtual address 0x116599000, protections were read-write

ALSO: How can I get rid of the error shown below? How do I turn off the debugger if the bugger is running? I clicked around in it at some point trying to learn about FF so maybe I turned something on...


7/8/14 2:06:48 AM kernel firefox (map: 0xe37ec2c) triggered DYLD shared region unnest for map: 0xe37ec2c, region 0x7fff81000000->0x7fff81200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

7/8/14 2:06:55 AM kernel Data/Stack execution not permitted: firefox[pid 177] at virtual address 0x116599000, protections were read-write I get this sort of error ALL THE TIME but noticed it now when just starting Firefox. 7/8/14 2:06:52 AM [0x0-0x1a01a].org.mozilla.firefox[177] Background starting... 7/8/14 2:06:55 AM kernel Data/Stack execution not permitted: firefox[pid 177] at virtual address 0x116599000, protections were read-write ALSO: How can I get rid of the error shown below? How do I turn off the debugger if the bugger is running? I clicked around in it at some point trying to learn about FF so maybe I turned something on... 7/8/14 2:06:48 AM kernel firefox (map: 0xe37ec2c) triggered DYLD shared region unnest for map: 0xe37ec2c, region 0x7fff81000000->0x7fff81200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

所有回复 (1)

guigs
guigs
more options

Does this also happen if you start Firefox in Safe Mode?

Try Firefox Safe Mode to see if the problem goes away. Firefox Safe Mode is a troubleshooting mode that turns off some settings, disables most add-ons (extensions and themes).

If Firefox is open, you can restart in Firefox Safe Mode from the Help menu:

  • In Firefox 29.0 and above, click the menu button New Fx Menu, click Help Help-29 and select Restart with Add-ons Disabled.
  • In previous Firefox versions, click on the Firefox button at the top left of the Firefox window and click on Help (or click on Help in the Menu bar, if you don't have a Firefox button) then click on Restart with Add-ons Disabled.

If Firefox is not running, you can start Firefox in Safe Mode as follows:

  • On Windows: Hold the Shift key when you open the Firefox desktop or Start menu shortcut.
  • On Mac: Hold the option key while starting Firefox.
  • On Linux: Quit Firefox, go to your Terminal and run firefox -safe-mode
    (you may need to specify the Firefox installation path e.g. /usr/lib/firefox)

When the Firefox Safe Mode window appears, select "Start in Safe Mode".
Safe Mode Fx 15 - Win

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article to find the cause.

To exit Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

When you figure out what's causing your issues, please let us know. It might help others with the same problem.