Closed
Bug 212197
Opened 21 years ago
Closed 20 years ago
memory balloons to over 200MB
Categories
(Core Graveyard :: GFX: Win32, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: nelomolen, Assigned: kmcclusk)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 loading up this page in mozilla 1.4 win32, and watching task manager... the computer starts to grind, then memory usage by mozilla gows up, up, and away. i closed the browser at 150MB, and killed the process after mozilla.exe had passed the 200MB mark. the website listed is the only example i have, and i have only tried this twice (with the same results). Reproducible: Always Steps to Reproduce: 1. go to http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/ and watch your memory usage 2. 3. Actual Results: memory usage steadily grows, at a certain point the browser becomes unusable and the process must be killed. Expected Results: hmm... not grown by *that* much, i guess. winxp w/sp1, 550mhz slot-a k7, 256mb ram
Comment 1•20 years ago
|
||
WFM. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040331 Microsoft Windows 2000 Professional 5.00.2195 SP4
Comment 2•20 years ago
|
||
Comfirmed(probably) with 2004042109(1.7 RC1,Zip Build)/Win-2K(SP4). Recreation scenario: (1) Start "Task Manager" of MS Windows 2000(or XP) and choose "process". Display "Memory used"(Probably real memory use) and "Virtual Memory Size". (2) Start Mozilla ("Image Name" is mozilla.exe) (3) Repeat "Open New Tab" and "Close Tab" -> "Virtual Momory Size" increases on tab open and decreases on tab close No problem. (4) Repeat "File/New/Navigatio Window" and close opened window -> "Virtual Momory Size" increases on open but doesn't decrease on close This is the problem. (5) Minimizing of window reduces "Memory used(probably used real memory)" to several Mega Bytes order. This indicates Real Momory is freed successufully. If new windows are opened by "Open link in new window" and if the page contains large data such as image, increasing virtual memory size in step (4) becomes large. Since real memory is freeed, there is no impact on memory use usually and this is not a critical problem. However, very large disk space for swap will be used. And this may casue memory management problem such as performance degradiation, becasuse memory management of MS Windows is not so well designed.
WFM Mozilla 2004042608 WinNT4 IMO this bug could be resolved as INVALID because this bug is about the example URL and the page doesn't seem to cause the reporter's problem. It's not reproducable. Comment 2 belongs to other bugs.
Comment 4•20 years ago
|
||
(In reply to comment #3) > Comment 2 belongs to other bugs. Oh sorry, I missunderstood this bug. example URL is WORKSFORME too. My comment 2 is probably one of the causes of Bug 215491. ( memory usage increases but never decreases) I' report to Bug 215491. Thanks.
Comment 5•20 years ago
|
||
Phil Barton, large virtual memory size problem exists as Bug 215491 / Bug 212197 says and I could recreate the problem on many window open/close when some kind of extentions such as Tab Browser Extention is used. However, this problem is apparanltly not caused by URL you mentioned as Anders Pedersen says. If you still experience large virtual storage problem, close this bug as invalid or worksforme, and join in Bug 215491.
Reporter | ||
Updated•20 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•