Bug 110223 - Web Inspector: release backtrace object group on each step
Summary: Web Inspector: release backtrace object group on each step
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Pavel Podivilov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-19 07:19 PST by Pavel Podivilov
Modified: 2013-02-19 08:14 PST (History)
10 users (show)

See Also:

Attachments
Patch (2.56 KB, patch)
2013-02-19 07:21 PST, Pavel Podivilov 		pfeldman: review+
webkit.review.bot: commit-queue-
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Podivilov 2013-02-19 07:19:38 PST 
Web Inspector: release backtrace object group on each step
Comment 1 Pavel Podivilov 2013-02-19 07:21:56 PST 
Created attachment 189085 [details]
Patch
Comment 2 WebKit Review Bot 2013-02-19 07:46:57 PST 
Comment on attachment 189085 [details]
Patch

Rejecting attachment 189085 [details] from commit-queue.

Failed to run "['/mnt/git/webkit-commit-queue/Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '--bot-id=gce-cq-02', 'validate-changelog', '--non-interactive', 189085, '--port=chromium-xvfb']" exit_code: 1 cwd: /mnt/git/webkit-commit-queue

/mnt/git/webkit-commit-queue/Source/WebCore/ChangeLog neither lists a valid reviewer nor contains the string "Unreviewed" or "Rubber stamp" (case insensitive).

Full output: http://queues.webkit.org/results/16614839
Comment 3 Andrey Adaikin 2013-02-19 07:57:17 PST 
Could you plz say more about the problem you are fixing? Is it memory leaks? What's a background of this problem (how did you find it)?
Comment 4 Pavel Podivilov 2013-02-19 08:07:37 PST 
Yes, it's a memory leak. I found it using about:memory page and then heap snapshots in inspector profiler.
Comment 5 Andrey Adaikin 2013-02-19 08:09:41 PST 
(In reply to comment #4)
> Yes, it's a memory leak. I found it using about:memory page and then heap snapshots in inspector profiler.

Nice! Thanks.
Comment 6 Pavel Podivilov 2013-02-19 08:14:36 PST 
Committed r143334: <http://trac.webkit.org/changeset/143334>