Closed Bug 676007 Opened 14 years ago Closed 13 years ago

Memory Leak? when running non stop NyanCat

Categories

(Core Graveyard :: Plug-ins, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 746009

People

(Reporter: nhirata, Unassigned)

Details

(Whiteboard: [MemShrink:P2][mozmill-test-needed][mozmill-endurance])

1. start with a fresh new profile 2. go to nyan.cat 3. minimize 4. run top and monitor every so often Expected: no leaking Actual: leaking? PID COMMAND %CPU TIME #TH #WQ #POR #MREG RPRVT RSHRD RSIZE VPRVT VSIZE PGRP PPID STATE UID FAULTS COW MSGSENT MSGRECV SYSBSD SYSMACH CSW PAGEINS USER 3359 firefox 16.2 00:01.90 23 1 173 601+ 57M+ 138M+ 116M+ 3359 firefox 2.4 00:02.55 23 1 173 617 58M+ 135M 117M+ 3359 firefox 2.6 00:03.70 22 1 171- 617- 57M- 138M 117M- 102M- 3475M- 3298 3359 firefox 2.5 00:04.83 22 1 171 619 58M 138M 118M 103M 3476M 3298 1 sleeping 501 35649 1027 190600+ 91902+ 25322+ 198522+ 19491+ 9 nhirata 3359 firefox 2.5 00:28.50 22 1 179 641 71M 142M 138M 117M 3495M 3298 1 sleeping 501 75969 1038 1184980+ 567349+ 111319+ 1234512+ 94969+ 16 3359 firefox 2.4 00:32.24 22 1 179 653 71M 142M 147M 117M 3502M 3298 1 sleeping 501 83927 1043 1366866+ 652977+ 123473+ 1424786+ 111238+ 16 3361- plugin-conta 5.3 00:39.61 12 2 190 298 8440K 58M 25M 48M 1025M 3298 3359 sleeping 501 8268 824 58105+ 26036+ 60827+ 292932+ 89024+ 1 nhirata 3359 firefox 2.2 00:33.09 23 2 181 655 71M 142M 147M 118M 3502M 3298 1 sleeping 501 83934 1043 1411944+ 675295+ 1 3359 firefox 2.5 00:46.99 22 1 178 655 72M 142M 147M 118M 3502M 3298 1 sleeping 501 93513 1043 2170377+ 1050770+ 176127+ 2264956+ 158141+ 33 3359 firefox 2.3 01:00.56 20 1 175 650 75M+ 142M 148M+ 123M 3501M 3298 1 sleeping 501 95859+ 1043 2763863+ 1347705+ 224567+ 2902589+ 199876+ 33 3359 firefox 2.7 01:14.73 21 1 177 659 76M 139M 149M 125M 3501M 3298 1 sleeping 501 107243 1043 3461326+ 1688892+ 272549+ 3635810+ 251452+ 33 3359 firefox 1.9 01:20.12 22 1 179 660 81M 139M 149M 125M 3501M 3298 1 sleeping 501 107904 1043 3734035+ 1824815+ 294184+ 3933323+ 272539+ 33 3359 firefox 5.8 01:40.72 23/1 1 199 702- 95M- 140M 172M- 138M- 3525M- 3298 1 running 501 171543 1043 4527073+ 2193871+ 364097+ 4758336+ 342967+ 34 Note: Shockwave Flash File: Flash Player.plugin Version: 10.1.102.64 Shockwave Flash 10.1 r102 MIME Type Description Suffixes application/x-shockwave-flash Shockwave Flash swf application/futuresplash FutureSplash Player spl Source Built from http://hg.mozilla.org/mozilla-central/rev/a43c3080f472 Build platform target i386-apple-darwin10.2.0 Mac OS X 10.6.7
Whiteboard: [MemShrink]
I tried this. I took measurements at start-up and 3.5 hours later: start-up 3.5 hours later -------- --------------- explicit 60.3MB 81.9MB js 25.0MB 34.1MB heap-unclassified 26.8MB 38.5MB resident 104.0MB 129.7MB Unfortunately I killed the process by accident and so didn't get a full about:memory snapshot for the 3.5-hours-later case. That doesn't tell us a great deal, but it's interesting that heap-unclassified grew so much.
Whiteboard: [MemShrink] → [MemShrink:P2]
Sounds interesting for an Endurance tests to verify a possible memory leak.
Whiteboard: [MemShrink:P2] → [MemShrink:P2][mozmill-test-needed][mozmill-endurance]
"I just don't understand why it's a cat head, and cat legs, and cat feet, attached to toes." But anyway, this sounds like fragmentation, modulo the small increase in heap-unclassified.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
> "I just don't understand why it's a cat head, and cat legs, and cat feet, attached to > toes." er, "attached to toast." :)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.