Bug 4576 - LEAK: using Pogo
Summary: LEAK: using Pogo
Status: RESOLVED DUPLICATE of bug 4599
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Dave Hyatt
URL: http://www.pogo.com
Depends on:
Reported: 2005-08-21 20:08 PDT by Andre Smith
Modified: 2005-08-23 14:30 PDT (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Andre Smith 2005-08-21 20:08:22 PDT
When I visit the www.pogo.com website, I am able to reproduce conditions that cause a memory leak in 
the Safari web browser. This occurs when I open the main page, but I have also noticed broswer crashes 
when using other portions of the site; I have included the output from the leaks command below:

console:~ asmith$ leaks Safari
Process 4076: 34833 nodes malloced for 7716 KB
Process 4076: 1 leak for 16 total leaked bytes.
Leak: 0x0b38ac60  size=16       string 'Safari'
Comment 1 John Sullivan 2005-08-23 14:30:15 PDT
The leak reported here is probably the PCFragPrepareClosureFromFile leak also reported in 4599. To 
verify, please do the following:

1. In a terminal window, set the environment variable MallocStackLogging to value 1 (e.g. in a bash shell, 
type "export MallocStackLogging=1<return>")
2. launch Safari from that terminal window, using run-safari or some other command-line technique
3. visit the page
4. in another terminal window, type 'leaks Safari'. This will show the backtraces of each reported leak.

*** This bug has been marked as a duplicate of 4599 ***