Status: Untriaged
Owner: ----
CC: [email protected],  [email protected],  [email protected],   
[email protected],  [email protected],  [email protected],   
[email protected],  [email protected],  [email protected]
Labels: Type-Bug Pri-2 OS-All Area-Misc Size-Medium

New issue 22932 by [email protected]: multiple valgrind errors showed up  
between build 155 and build 160 on linux valgrind bot 2
http://code.google.com/p/chromium/issues/detail?id=22932

Sorry for the vague description and copying you all to Cc. The linux
valgrind bot timed out in build 156-159 and you landed something in
between.

(time-out issue was taken care of).

After identifying the cause, the description has to be chnaged. If there
are multiple causes, it has to be split to multiple bugs.

http://build.chromium.org/buildbot/waterfall/builders/Linux%20Tests%20(valg
rind)(2)/builds/160/steps/valgrind%20test:%20ui/logs/stdio

has 6 valgrind errors. The last one is not new and a bug was filed against
the leak (bug 22923)

The first 4 all come from running chrome --type=zygote --enable-logging=
and the amount of memory leaked is small. (a dozen bytes each).

The 5th comes from running WorkerTest.MultipleWorkers and leaks tens of
kBs.

chrome --no-first-run --no-default-browser-check --enable-file-cookies --
testing-channel=ChromeTestingInterface:32038.1 --homepage=about:blank --
disable-web-resources --user-data-
dir=/tmp/org.chromium.5RDWCM/test_user_data --metrics-recording-only --
enable-logging --test-name=WorkerTest.MultipleWorkers


The 6th one (which is not new) also comes from the same test, but has a
different stack. Perhaps, the 5th one has to be merged to issue 22923.







--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to