A few of these, where root cause is the same (leaking of tasks, for example
11462, 6, 11144 among others) should get fixed once
http://codereview.chromium.org/115328 gets committed.
On Wed, May 13, 2009 at 5:23 PM, Evan Martin wrote:
>
> And the award goes to...
>
> % git log origin --since=yesterday --grep=valgrind -i --pretty='format:%an
> %s'
> thes...@chromium.org Split NetUtilTest.IDNToUnicode into IDNToUnicodeFast
> e...@chromium.org valgrind: print the gtest suppression list on startup.
>
> Wait, we've had *one* fix so far? :~( (Mine doesn't count, as it's a
> one-liner for logging.)
> I guess there's room for some others where someone didn't mention
> valgrind in their commit message.
>
> I've made progress on two more bugs, but that leaves pretty much all
> the rest unclaimed.
>
> http://code.google.com/p/chromium/issues/list?can=2&q=label:valgrind
>
> On Mon, May 11, 2009 at 2:20 PM, Dan Kegel
> wrote:
> >
> > We've been using Valgrind to find memory leaks, pointer errors, and race
> > conditions in Chromium on Mac and Linux for a while now.
> > (See the valgrind bots at http://build.chromium.org.)
> > That's cool, but it would be even cooler if we actually fixed the
> > problems Valgrind has found. According to
> > http://code.google.com/p/chromium/issues/list?q=valgrind
> > we've fixed 24 Valgrind issues already, but there are 60 still open.
> >
> > So let's do something about it! The first step is for you to visit
> > http://dev.chromium.org/developers/how-tos/using-valgrind
> > and learn about how to use Valgrind to find problems in Chromium.
> >
> > A few Chromium developers (playmobil, jhawkins, thestig, and myself)
> > are going to host a Valgrind Fixit this Wednesday and Thursday,
> > May 13th and 14th. We'll be available on the chromium irc channel
> > (irc.freenode.net/#chromium) to help you get started using Valgrind
> > with Chromium. The page linked above also has suggestions for
> > what to do during the Fixit. (For instance, be sure to put a note
> > in the bug report saying you've started fixing the bug, so nobody
> > else duplicates your effort.)
> >
> > As incentive for people to help out, we will send a Valgrind mug to
> > whoever contributes the best Valgrind-related fixes, bug reports,
> > and/or triage during those two days (winner will be chosen at the
> > discretion of the valgrind fixit judging panel).
> >
> > Thanks, and see you at the Fixit!
> > - Dan
> >
> > p.s. And thanks to Julian Seward of http://valgrind.org for providing
> > such a wonderful tool!
> >
> > >
> >
>
> >
>
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---
