Closed
Bug 323672
Opened 19 years ago
Closed 17 years ago
No Memory Dump after closing application
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mclo, Unassigned)
References
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: Firefox 1.5 After closing Firefox, the software hangs in system memory. The process is still visible under Windows Task Mamanger. Reproducible: Always Steps to Reproduce: 1.Open Firefox 2. Use it for some time and open some tabs 3. Check memory usage using Windows Task Manager (CRL+ATL+ESC) 4. Close Firefox 5. Check Windos Task Manager Again The process should disappear from Windows Task Manager
Comment 1•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060115 Firefox/1.6a1 ID:2006011604 WFM. Have you also tried it with disabled extensions or with a new profile?
Comment 2•17 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/2007051502 Firefox/2.0.0.4 WFM. I had this sort of thing happen after running Firefox 1.5 for a long time (days or weeks). It would get to the point where it was consuming 200-300MB of memory, and the process of closing the application and freeing memory (as viewed in the Task Manager) would take an inordinately long time. I haven't had it happen with 2.x yet, IIRC, and I still leave my browser open for long periods of time.
Comment 3•17 years ago
|
||
Closing as INCOMPLETE because comment 1 was not addressed. Please provide more information about this if you're able.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•