Comment #6 on issue 15818 by bugdro...@chromium.org: Mem leak in
BlockedPopupContainerView::Create
http://code.google.com/p/chromium/issues/detail?id=15818
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=revrevision=19942
Comment #7 on issue 15818 by bugdro...@chromium.org: Mem leak in
BlockedPopupContainerView::Create
http://code.google.com/p/chromium/issues/detail?id=15818
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=revrevision=19944
Updates:
Status: Fixed
Comment #8 on issue 15818 by pinker...@chromium.org: Mem leak in
BlockedPopupContainerView::Create
http://code.google.com/p/chromium/issues/detail?id=15818
(No comment was entered for this change.)
--
You received this message because you are listed in the
Comment #9 on issue 15818 by bugdro...@chromium.org: Mem leak in
BlockedPopupContainerView::Create
http://code.google.com/p/chromium/issues/detail?id=15818
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=revrevision=19948
Comment #5 on issue 15818 by nirnim...@chromium.org: Mem leak in
BlockedPopupContainerView::Create
http://code.google.com/p/chromium/issues/detail?id=15818
Pink, this is reproducible on my machine synced to the ToT.
Putting in the line numbers:
16:57:15 __init__.py [ERROR]
Comment #1 on issue 15818 by pinker...@chromium.org: Mem leak in
BlockedPopupContainerView::Create
http://code.google.com/p/chromium/issues/detail?id=15818
I'm not seeing this locally or on the bot. What's up?
--
You received this message because you are listed in the owner
or CC fields of
Comment #2 on issue 15818 by o...@chromium.org: Mem leak in
BlockedPopupContainerView::Create
http://code.google.com/p/chromium/issues/detail?id=15818
I thought Mike fixed these yesterday. Nirnimesh, are you sure these errors
are still
happening?
--
You received this message because you
Updates:
Status: WontFix
Comment #3 on issue 15818 by nirnim...@chromium.org: Mem leak in
BlockedPopupContainerView::Create
http://code.google.com/p/chromium/issues/detail?id=15818
I did see the leak in 3 valgrind cycles after Mike's fix.
Not any more though.
--
You received this
Updates:
Status: Assigned
Comment #4 on issue 15818 by o...@chromium.org: Mem leak in
BlockedPopupContainerView::Create
http://code.google.com/p/chromium/issues/detail?id=15818
OK. I still see the following error on the bots, but it's flaky. Reopening.
1,312 (44 direct, 1,268
