Any chance of simple auto debug for plug ins?
How about logging entry and exit points for each plug in that runs? Then it should be pretty easy to identify which plugin is crashing. Sure, it won't work all the time, but it'll work much of the time.
This would be SO much easier than taking ages to manually debug by safe mode, trouble shooting, disabling each plugin one at a time. That's no fun, even for IT pros. Think what it's like for regular users!
What am I missing here? This sounds like a very simple fix, which would offer HUGE wins for little work.
How does that sound?
Ed
所有回复 (7)
Hi,
The people who answer questions here, for the most part, are other users volunteering their time (like me), not Mozilla employees or developers. If you want to leave feedback for developers, you can go to the Firefox Help menu and select Share ideas and feedback…. Alternatively, you can use this link. Your feedback gets collected by a team of people who read it and gather data about the most common issues.
You can also file a bug report or feature request. See File a bug report or feature request for Mozilla products for details.
Ok, thanks. I'd still like to know if it's a good idea, or if it's more complex than that.
Note that Plugins (NPAPI) have not been supported for a good while now https://support.mozilla.org/en-US/kb/npapi-plugins
I take it you are actually referring to Extensions.
I have no idea, I'm talking about whatever you call things that you can download to add functionality. e.g. tree style tabs, ad blockers, etc.
You can find add-ons' debug entries in the Browser Console (Ctrl + Shift + J) or Browser Tools (Ctrl + Alt + Shift + i).
由TyDraniu于修改
Thanks, that's definitely worth knowing and trying.
The interaction between extensions and websites is complex and intertwined. Errors may appear to come from the website but be caused by an extension and vice versa. Disabling extensions through a process of trial and error is the easiest way for non-technical users to identify which one is responsible.