Closed
Bug 284016
Opened 20 years ago
Closed 19 years ago
DOMWINDOW count not going to zero when using radiogroup.selectedIndex within a Modal Dialog
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: marty, Assigned: bugzilla)
Details
(Keywords: memory-leak)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Xul code:
<row align="start">
<hbox flex="1" pack="end" align="end">
<label class="fieldname" value="Status"/>
<spacer width="5px"/>
</hbox>
<radiogroup id="mr_record_status" orient="horizontal">
<radio id="mr_status_open" label="Open" selected="true"/>
<radio id="mr_status_closed" label="Closed"/>
</radiogroup>
</row>
Javascript code:
if ( document.getElementById( "mr_record_status" ).selectedIndex == 0 ) {
....
}
where "mr_record_status" is a radiogroup causes the DomWindow count to not
decrement to 0
The work around is:
if ( document.getElementById( "mr_status_open" ).selected ) {
....
}
where "mr_status_open" is a radio button.
When closing the browser, the DomWindow count stays greater than 0. Everytime
the code is executed, in my case a Modal Dialog that is open and closed, the
DOMWindow count increments by 2. The following out is what I have in a debug build:
--WEBSHELL == 1
--DOMWINDOW == 4
--WEBSHELL == 0
--DOMWINDOW == 3
nsPluginHostImpl::Observe "xpcom-shutdown"
WARNING: nsExceptionService ignoring thread destruction after shutdown, file
c:/firefox/mozilla/xpcom/base/nsExceptionService.cpp, line 191
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file
c:/firefox/mozilla/toolkit/components/history/src/nsGlobalHistory.cpp, line 2520
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(OpenDB())) failed, file
c:/firefox/mozilla/toolkit/components/history/src/nsGlobalHistory.cpp, line 1221
nsPluginHostImpl dtor
--DOMWINDOW == 2
JS engine warning: 1 atoms remain after destroying the JSRuntime.
These atoms may point to freed memory. Things reachable
through them have not been finalized.
nsStringStats
=> mAllocCount: 12982
=> mReallocCount: 1548
=> mFreeCount: 12978
=> mShareCount: 15046
=> mAdoptCount: 2577
=> mAdoptFreeCount: 2576
Reproducible: Always
Comment 1•20 years ago
|
||
Could you try reproducing it on a recent nightly build?
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•