Closed Bug 620218 Opened 9 years ago Closed 9 years ago
.options .strict enabled and any console service is attached
This issue can be seen with Firebug v1.7 and Mozmill installed within a profile. Follow this steps in a fresh profile to reproduce the hang and memory usage as given in comment 0: 1. Install the latest version of Firebug: http://getfirebug.com/releases/firebug/1.7X/ 2. Install the latest alpha version of Firebug 1.7 3. Install Mozmill: https://addons.mozilla.org/en/firefox/addon/9018/ 4. Restart the browser 5. Load the URL After step 5 you will notice the hang and high memory usage.
Summary: Loading Google Chrome releases blog post hangs browser while using >1GB of additional memory → Loading a web page hangs browser (>1GB of additional memory usage) with Firebug and Mozmill installed
Hi Henrik, please cc email@example.com on Firebug issues, thanks. We can't do any work on JS debug for now on FF4.0, it's just broken we have to wait.
(In reply to comment #4) > So, my guess is that there is a collision between these two extensions. I don't think you should limit your bug hunt to this scenario. I have never installed the Mozmill extension yet I have experienced the >1GB memory footprint. The problem also manifested itself after a nightly build update (which one I do not recall) not after a Firebug update - meaning I had been using the current version of Firebug prior to the large memory footprint issue. Hope that helps. Chris
Do you have a specific steps-to-reproduce (something like you can see in Comment #1) that I could follow to reproduce the problem on my machine? Honza
(In reply to comment #4) > Is Mozmill somehow inspecting/exploring the chrome space? We check for load, DOMContentLoaded, and beforeunload events. That's everything. See: https://github.com/mozautomation/mozmill/blob/hotfix-1.5.2/mozmill/mozmill/extension/resource/modules/init.js#L58 Jan, even with Firebug disabled, are there still some components, which are active?
So, after some time debugging the debugger I noticed that the problem is somehow related to the nsIConsoleService. If Firebug registers a listener to it, the problem appears. Note that just the registration itself causes the problem. Even if the observer method (called when an error happens) is empty the problem is there. Does Mozmill touches the nsIConsoleService? Honza
Yes, at some places we are using the nsIConsoleService service to log messages (logStringMessage), but that's all as far as I can find.
I am attaching a test extension that does nothing but registering a console listener. Please, repeat steps from comment #1 and use this extension instead of Firebug. The bug is clearly reproducible. If you disable Mozmill, the problem is gone. The next step: can you take a look at Mozmill code and step by step find the place which causes the problem? It looks to me as a platform bug, but somebody should check Mozmill first. Honza
Boris, I know it could be a problem with Mozmill, but asking in advance if you have any ideas about what could be wrong... Honza
> Once a listener is around, marshaling between js and c++ land is performed I > guess, which causes the high memory consumption. Possibly, but more likely the listener is just holding to all the messages.
Rob, Kevin, I have cc-ed you since HUD is now involved in this bug and you could have some more ideas what is wrong. One thing I don't understand why the bug is only reproducible when Mozmill is installed. Is somebody willing to check Mozmill? Honza
I can reproduce it without Mozmill now. Thanks Nils. Updating summary. What's the best component for this bug?
OS: Mac OS X → All
Hardware: x86 → All
Summary: Loading a web page hangs browser (>1GB of additional memory usage) with Firebug and Mozmill installed → Loading a web page hangs browser (>1GB of additional memory usage) with Firebug installed and js strict warnings enabled
No longer blocks: 624408
Duplicate of this bug: 624408
There is probably some performance analysis and tuning we can do with the Web Console so we're not bogging down under the onslaught of these messages. I'll move it to devtools. For Firebug, you may want to open an issue around "7000+ strict warnings makes the console slow".
Component: General → Developer Tools
QA Contact: general → developer.tools
(In reply to comment #20) > For Firebug, you may want to open an issue around "7000+ strict warnings makes > the console slow". Just based on trying FF4.0b9pre for a few days, it definitely feels like logging is significantly slower than on FF3.6. I have no idea why.
I'm marking this as a dup of bug 634444, even though this bug existed earlier, because the discussion in that bug is clearer.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 634444
You need to log in before you can comment on or make changes to this bug.