We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From timurrrr@google.com on May 05, 2011 10:09:14
http://build.chromium.org/p/client.drmemory/builders/win-vista_x64-drm/builds/948/steps/Run%20TSan%20tests/logs/summary%3A%202%20report%28s%29 0x77ca081d <ntdll.dll+0x7081d> ntdll.dll!RtlInitOutOfProcessMemoryStream 0x77c5d6f4 <ntdll.dll+0x2d6f4> ntdll.dll!RtlInitializeCriticalSection racecheck_unittest-windows-x86-O0.exe!Mutex::Mutex thread_wrappers_win.h:82 racecheck_unittest-windows-x86-O0.exe!StressTests_ManyLockSetsTest::StressTests_ManyLockSetsTest_Test::TestBody racecheck_unittest.cc:1438
This is a test https://code.google.com/p/data-race-test/source/browse/trunk/unittest/racecheck_unittest.cc?spec=svn3420&r=3413#1415 which allocates-deallocates 13 mutexes and does 2^13 Lock-Unlocks on them from two different threads.
Not sure how it could cause some extra leak. // Maybe symbols are wrong again?
Original issue: http://code.google.com/p/drmemory/issues/detail?id=385
The text was updated successfully, but these errors were encountered:
From bruen...@google.com on May 05, 2011 07:46:33
need to analyze those Rtl routines, could be something unusual going on in there, such as happened in issue #306
Sorry, something went wrong.
No branches or pull requests
From timurrrr@google.com on May 05, 2011 10:09:14
http://build.chromium.org/p/client.drmemory/builders/win-vista_x64-drm/builds/948/steps/Run%20TSan%20tests/logs/summary%3A%202%20report%28s%29 0x77ca081d <ntdll.dll+0x7081d> ntdll.dll!RtlInitOutOfProcessMemoryStream
0x77c5d6f4 <ntdll.dll+0x2d6f4> ntdll.dll!RtlInitializeCriticalSection
racecheck_unittest-windows-x86-O0.exe!Mutex::Mutex
thread_wrappers_win.h:82
racecheck_unittest-windows-x86-O0.exe!StressTests_ManyLockSetsTest::StressTests_ManyLockSetsTest_Test::TestBody
racecheck_unittest.cc:1438
This is a test https://code.google.com/p/data-race-test/source/browse/trunk/unittest/racecheck_unittest.cc?spec=svn3420&r=3413#1415 which allocates-deallocates 13 mutexes and does 2^13 Lock-Unlocks on them from two different threads.
Not sure how it could cause some extra leak.
// Maybe symbols are wrong again?
Original issue: http://code.google.com/p/drmemory/issues/detail?id=385
The text was updated successfully, but these errors were encountered: