Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(228)

Issue 293042: Remove ThreadSanitizer suppression for 22272.... (Closed)

Created:
11 years, 2 months ago by eroman
Modified:
9 years, 6 months ago
Reviewers:
Timur Iskhodzhanov
CC:
chromium-reviews_googlegroups.com, not_the_right_glider, Nirnimesh, dank, stuartmorgan, pam+watch_chromium.org
Visibility:
Public.

Description

Remove ThreadSanitizer suppression for 22272. The race was specific to unit-test code (see r29826) and should be fixed now. BUG=22272 Committed r30301.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+0 lines, -7 lines) Patch
M tools/valgrind/tsan/suppressions.txt View 1 chunk +0 lines, -7 lines 0 comments Download

Messages

Total messages: 8 (0 generated)
eroman
11 years, 2 months ago (2009-10-21 04:39:13 UTC) #1
Timur Iskhodzhanov
LGTM
11 years, 2 months ago (2009-10-21 09:38:29 UTC) #2
Timur Iskhodzhanov
Cancelling my LGTM, some race on LoadLog is still present! Here is one of the ...
11 years, 2 months ago (2009-10-21 10:58:50 UTC) #3
eroman
Hmm, that looks like a bug in the socket stream unittest -- from that callstack ...
11 years, 2 months ago (2009-10-21 17:04:11 UTC) #4
eroman
Actually scratch my comment, dunno what this is. looking... On Wed, Oct 21, 2009 at ...
11 years, 2 months ago (2009-10-21 17:13:52 UTC) #5
Timur Iskhodzhanov
I don't see this report anymore. Do you know whether it was fixed?
11 years, 1 month ago (2009-10-27 15:30:39 UTC) #6
eroman
On Tue, Oct 27, 2009 at 8:30 AM, <timurrrr@chromium.org> wrote: > I don't see this ...
11 years, 1 month ago (2009-10-27 19:14:33 UTC) #7
Timur Iskhodzhanov
11 years, 1 month ago (2009-10-27 19:43:29 UTC) #8
I've taken a look at http://codereview.chromium.org/320003/diff/1/2
It looks like ThreadSanitizer didn't catch the synchronization using
base::WaitForSingleProcess which was called by WaitForFinish.

I'll take a closer look, it may be a bug in ThreadSanitizer!

Go ahead and commit this changelist

On 2009/10/27 19:14:33, eroman wrote:
> On Tue, Oct 27, 2009 at 8:30 AM,  <mailto:timurrrr@chromium.org> wrote:
> > I don't see this report anymore.
> > Do you know whether it was fixed?
> 
> Yeah, so I believe I stopped the bug from reproducing when I committed:
> 
>     http://codereview.chromium.org/320003
> 
> I still don't understand the exact circumstances of the race, other
> than it had to do with with the specific setup in this unit-test. The
> unit-test was using TestServer::SendQuit(), which I found does weird
> stuff (it spins up another IO thread, so we end up with multiple IO
> threads). I changed the test not to use that anymore.
> 
> Anyway, I can probably go ahead and commit the suppression removal.
> 
> As follow-up I would still like to better understand how this setup
> caused the race, since it doesn't look like the two threads were
> sharing states.
> 
> The particular race is specific to the unit-test setup, which ends up
> using two IO threads (the network objects are all non thread safe).
> 
> Thanks for your patience.
> 
> >
> > http://codereview.chromium.org/293042
> >

Powered by Google App Engine
This is Rietveld 408576698