Closed
Bug 502785
Opened 15 years ago
Closed 14 years ago
OOM when try to debug javascript in firefox using firebug 1.3.2
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mantri.puja, Unassigned)
Details
(Whiteboard: [CLOSEME 2010-11-01])
Attachments
(1 file)
538 bytes,
text/html
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; MS-RTC LM 8)
Build Identifier: version : 3.0.11
Firefox always run into out of memory when try to debug the web application.
Reproducible: Always
Steps to Reproduce:
1.run a web application in firefox
2.put a breakpoint at some javascript code
3.start debuging the application.
Actual Results:
Out of memory exception occurs on the console. It does not stop the application.
Expected Results:
It should not throw the out of memory exception.
The firefox version I am using is 3.0.11
firebug version is 1.3.2
Version: unspecified → 3.0 Branch
Does this happen with Firefox 3.5? Does it happen in Firefox's safe mode? Can you give an example of a web application you can reproduce this with?
I get following message on the consol when I debug the simple application like attached file test.html
Firebug cannot find firebugCommandLineAttached attribute on firebug console element, its too early for command line <div id="_firebugConsole" style="display: none;" FirebugVersion="1.3.2" methodName="evaluate" expr="with(_FirebugCommandLine){str };"> Window test.htm
Along with this kind of messages, I get the OOM issue if I debug my application. I cannot disclose the details. But in the application we create lot of javascript objects in memory. That might be causing the OOM.
I did not test the application on firefox 3.5. I will test it on firefox 3.5 and let you know the result.
Comment 4•14 years ago
|
||
This is a mass search for Firefox General bugs filed against version 3.0 that are UNCO and have not been changed for 200 days.
Reporter, please update to Firefox 3.6.10 or alter. Firefox 3.0 is no longer supported and is no longer receiving updates. After you update, please create a fresh profile, http://support.mozilla.com/kb/managing+profiles, and test to see if your bug still exists. If you still the bug, then please post a comment with the version you tested against, and the problem. If the issue is no longer there, please set the RESOLUTION to RESOLVED, WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
Comment 5•14 years ago
|
||
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•