Closed
Bug 11372
Opened 25 years ago
Closed 25 years ago
Crash after browsing for a while.
Categories
(Core :: Networking: Cache, defect, P3)
Tracking
()
VERIFIED
INVALID
M12
People
(Reporter: cathy, Assigned: gagan)
Details
(Whiteboard: help wanted)
Attachments
(3 files)
I pulled out the source of SeaMonkey by CVS to develop my own project since the
beginning of this year. I also update my mozilla source tree every Monday. But,
it has been a long time I found that the browser seems dosen't free its memory
so that it will run out of the memory after browsing many web pages, whatever
viewer or the apprunner. Even the M8 version or the newest one I pull out is so.
Updated•25 years ago
|
Summary: Crash after browsing for a while.
Comment 1•25 years ago
|
||
Necko memleak? Added summary.
Comment 2•25 years ago
|
||
I don't know if this bug report has enough detail for gagan to go on. There are
other bug reports dealing specifically with memory leaks. Gagan?
The attachment I post is a page that will change its picture every 5 seconds. If
you use linux command 'top' to view the memory usage of viewer(M8), you will
find the memory size of viewer will grow when the picture changes. After running
a period of time, it will run out of the system memory.
Comment 7•25 years ago
|
||
neither of these testcases work on a recent build could you create another one
that does work?
Status: NEW → ASSIGNED
Whiteboard: help wanted
Target Milestone: M12
Am not sure this is cache related. Volunteers help me clarify this.
Comment 9•25 years ago
|
||
I don't understand how this could be cache-related if there's no caching code in
the browser.
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Comment 10•25 years ago
|
||
the attachment doesn't work, we need more specific steps to reproduce, plus the
component is set incorrectly, marking invalid.
Cathy, please come up with a new testcase or more reproducible steps, thanks
Reporter | ||
Comment 11•25 years ago
|
||
Reporter | ||
Comment 12•25 years ago
|
||
Use M9 viewer to run the attachment(id=1829) will cause viewer's core memory to
grow. (You can see this form the output message of 'top' command). The memory
usage of the attachmemt(id=1226) in M9 is normal.
I am not sure if the attachment(id=1829) will work. If not, pls use browser's
"view source" utility to view the source of the attachment and download it.
Then, you can test it in the viewer.
Comment 13•25 years ago
|
||
Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache
component.
You need to log in
before you can comment on or make changes to this bug.
Description
•