Comment #16 on issue 10737 by bugdro...@chromium.org: Memory leak in
BrowserWindowGtk::ConnectAccelerators
http://code.google.com/p/chromium/issues/detail?id=10737
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=23078
---
Updates:
Owner: de...@chromium.org
Comment #15 on issue 10737 by de...@chromium.org: Memory leak in
BrowserWindowGtk::ConnectAccelerators
http://code.google.com/p/chromium/issues/detail?id=10737
(No comment was entered for this change.)
--
You received this message because you are lis
Comment #13 on issue 10737 by bugdro...@chromium.org: Memory leak in
BrowserWindowGtk::ConnectAccelerators
http://code.google.com/p/chromium/issues/detail?id=10737
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=20050
---
Comment #11 on issue 10737 by d...@chromium.org: Memory leak in
BrowserWindowGtk::ConnectAccelerators
http://code.google.com/p/chromium/issues/detail?id=10737
Heh. Now it's showing up in the reference build.
Should we update our reference build?
1,036 (740 direct, 296 indirect) bytes in 37 b
