Closed Bug 38271 Opened 25 years ago Closed 24 years ago

nsWebShell not released correctly.

Categories

(Core Graveyard :: Embedding: APIs, defect, P1)

Product:
Core Graveyard
Component:
Embedding: APIs
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: edburns, Assigned: jud)

Details

(Keywords: embed, memory-leak, Whiteboard: [nsbeta3-])

For some reason, the refcount of the nsWebShell instance held by initContext is 2 at the time the user calls nativeDestroyInitContext. It should be one. The webshell instance isn't getting properly deleted.
I filed it. I accept it.
Status: NEW → ASSIGNED
As of M16, the refcount goes to 1 at window close time, but never to 0. Since the webshell/docshell is such a heavily refcnt'd interface, I'm re- assigning to embedding. There should be an API call to "deallocate all resources associated with a window."
Assignee: edburns → valeski
Status: ASSIGNED → NEW
Component: Java APIs to WebShell → Embedding APIs
QA Contact: geetha.vaidyanaathan → jrgm
Keywords: mlk, nsbeta3
Whiteboard: [nsbeta3+]
Target Milestone: --- → M18
miraculously I'm seeing the shell count goto zero now on linux and windows.
need a reproducible case.
Priority: P3 → P1
per email with Jud, changing nsbeta3+ to nsbeta3- on all "embed" keyword bugs and Embedding component bugs since embedding changes will not be made in the mn6 branch. If you feel this bug fix needs to go into mn6 branch, please list the reasons/user impact/risk and nominate for rtm. Thanks.
Whiteboard: [nsbeta3+] → [nsbeta3-]
Keywords: embed
WFM
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updating QA Contact
QA Contact: jrgm → mdunn
WFM
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.