New issue
Advanced search Search tips

Issue 805388 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 788948
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

AddressSpaceRandomizationTest.Unpredictable is flaky

Project Member Reported by gab@chromium.org, Jan 24 2018

Issue description

When running "base_unittests.exe --test-launcher-jobs=42" on Z840 (Win10), I easily get:

[ RUN      ] AddressSpaceRandomizationTest.Unpredictable
[14928:71616:0124/123722.581:163269671:FATAL:address_space_randomization_unittest.cc(81)] Check failed: 0ULL == addresses.count(address) (0 vs. 1)
Backtrace:
        base::debug::StackTrace::StackTrace [0x68B9A170+32] (D:\src\chrome2\src\base\debug\stack_trace_win.cc:286)
        base::debug::StackTrace::StackTrace [0x68B9966D+13] (D:\src\chrome2\src\base\debug\stack_trace.cc:199)
        logging::LogMessage::~LogMessage [0x68BC9ED7+87] (D:\src\chrome2\src\base\logging.cc:581)
        base::AddressSpaceRandomizationTest_Unpredictable_Test::TestBody [0x008EF473+611] (D:\src\chrome2\src\base\allocator\partition_allocator\address_space_randomization_unittest.cc:81)
        testing::Test::Run [0x0093F928+178] (D:\src\chrome2\src\third_party\googletest\src\googletest\src\gtest.cc:2473)
        testing::TestInfo::Run [0x009402BE+204] (D:\src\chrome2\src\third_party\googletest\src\googletest\src\gtest.cc:2651)
        testing::TestCase::Run [0x00940796+238] (D:\src\chrome2\src\third_party\googletest\src\googletest\src\gtest.cc:2769)
        testing::internal::UnitTestImpl::RunAllTests [0x00945877+631] (D:\src\chrome2\src\third_party\googletest\src\googletest\src\gtest.cc:4665)
        testing::UnitTest::Run [0x009454B8+156] (D:\src\chrome2\src\third_party\googletest\src\googletest\src\gtest.cc:4277)
        base::TestSuite::Run [0x0096BD88+104] (D:\src\chrome2\src\base\test\test_suite.cc:281)
        base::`anonymous namespace'::LaunchUnitTestsInternal [0x0096D29B+281] (D:\src\chrome2\src\base\test\launcher\unit_test_launcher.cc:214)
        base::LaunchUnitTests [0x0096D12E+146] (D:\src\chrome2\src\base\test\launcher\unit_test_launcher.cc:558)
        main [0x0096BABB+119] (D:\src\chrome2\src\base\test\run_all_base_unittests.cc:12)
        __scrt_common_main_seh [0x00A12E7A+248] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:283)
        BaseThreadInitThunk [0x76D162C4+36]
        RtlSubscribeWnfStateChangeNotification [0x778E0F79+1081]
        RtlSubscribeWnfStateChangeNotification [0x778E0F44+1028]


@bbudge who touched partition_allocator most recently (sorry..!)

 

Comment 1 by bbudge@chromium.org, Jan 30 2018

Status: Started (was: Assigned)

Comment 2 by palmer@chromium.org, Jan 30 2018

Cc: palmer@chromium.org tsepez@chromium.org
Components: Blink>MemoryAllocator>Partition
Does this happen only on Windows?

Comment 3 by palmer@chromium.org, Jan 30 2018

I'm not able to reproduce it on Windows 10/Z840, with ToT from this morning.

On Rodete/Z840, I get other Partition Alloc test failures, but that's with a checkout from yesterday. Updating it now and trying again...

Comment 4 by palmer@chromium.org, Jan 30 2018

After a fresh checkout on Linux, I get failures like this:

```
~/chromium/src $ ./out/Default/base_unittests --test-launcher-jobs=42
...
../../base/allocator/partition_allocator/partition_alloc_unittest.cc:2128: Failure
Expected equality of these values:
  IsPageInCore(ptr1 - kPointerOffset + (kSystemPageSize * 3))
    Which is: true
  false
[  FAILED  ] PartitionAllocTest.PurgeDiscardable (3 ms)
```

Comment 5 by bbudge@chromium.org, Jan 31 2018

Mergedinto: 788948
Status: Duplicate (was: Started)

Sign in to add a comment