[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 Comment #9 by [EMAIL PROTECTED]: This is now finished; lets track existing issues through new bugs. Memory issues were the main cause. Issue attribute updates: Status: Fixed -- Yo

[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 Comment #8 by [EMAIL PROTECTED]: A big part of the perf problem was just the memory leaks. After fixing the V8EventListener leak (caused by changes to RefCountable) yesterday, the page-cycl

[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 Comment #7 by [EMAIL PROTECTED]: I'm looking at the intl1 issues now. I don't believe it's DOM bindings leaking here; I ran through the intl1 page cyclers with 0 leaked nodes. But, still t

[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 Comment #6 by [EMAIL PROTECTED]: Looks like page-cycler-moz was fixed by r2891 (http://src.chromium.org/viewvc/chrome? view=rev&revision=2891). The international page cyclers don't seem to

[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 Comment #5 by [EMAIL PROTECTED]: Issue attribute updates: Cc: [EMAIL PROTECTED] -- You received this message because you are listed in the owner or CC fields of this issue, or b

[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 Comment #4 by [EMAIL PROTECTED]: Mike thinks this may be related to leaks. I'm passing to him. Issue attribute updates: Owner: [EMAIL PROTECTED] -- You received this message becaus

[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 Comment #3 by [EMAIL PROTECTED]: (No comment was entered for this change.) Issue attribute updates: Labels: -Pri-1 Pri-0 -- You received this message because you are listed in the

[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 Comment #2 by [EMAIL PROTECTED]: (No comment was entered for this change.) Issue attribute updates: Owner: --- -- You received this message because you are listed in the owner or C

[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 Comment #1 by [EMAIL PROTECTED]: Startup regression is now tracked in issue 3051. Issue attribute updates: Labels: WebKitMerge -- You received this message because you are listed i

[chromium-bugs] Issue 3050 in chromium: fix perf regressions after the merge

Issue 3050: fix perf regressions after the merge http://code.google.com/p/chromium/issues/detail?id=3050 New issue report by [EMAIL PROTECTED]: This should should probably be split up into smaller bugs: 7% page-cycler-moz regression: http://build.chromium.org/buildbot/perf/xp-release-dual-core/m