Bug 4576
| Summary: | LEAK: using Pogo | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andre Smith <andre-smith> |
| Component: | New Bugs | Assignee: | Dave Hyatt <hyatt> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | 420+ | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
| URL: | http://www.pogo.com | ||
Andre Smith
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'
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
John Sullivan
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 ***