Issue metadata
Sign in to add a comment
|
browser_tests failing on chromium.mac/Mac10.13/10.12 because of Crashpad |
||||||||||||||||||||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of rhalavati@google.com browser_tests (experimental) failing on chromium.mac/Mac10.13 Tests Builders failed on: - Mac10.13 Tests: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.13%20Tests
,
Jun 14 2018
,
Jun 14 2018
The failure call stack is: RUN ] Native/ExtensionBindingsApiTest.UnavailableBindingsNeverRegistered/0 [0614/033331.550269:ERROR:mach_extensions.cc(68)] bootstrap_check_in org.chromium.crashpad.child_port_handshake.76058.1075938.EXALSLXNPGZCVSZG: unknown error code (141) [0614/033331.550625:FATAL:child_port_handshake.cc(111)] Check failed: server_port.is_valid(). 0 crashpad_handler 0x000000010344d58c base::debug::StackTrace::StackTrace(unsigned long) + 28 1 crashpad_handler 0x000000010343a3c1 logging::LogMessage::~LogMessage() + 225 2 crashpad_handler 0x0000000103457274 crashpad::ChildPortHandshake::RunServerForFD(base::ScopedGeneric<int, base::internal::ScopedFDCloseTraits>, crashpad::ChildPortHandshake::PortRightType) + 516 3 crashpad_handler 0x0000000103429266 crashpad::HandlerMain(int, char**, std::__1::vector<std::__1::unique_ptr<crashpad::UserStreamDataSource, std::__1::default_delete<crashpad::UserStreamDataSource> >, std::__1::allocator<std::__1::unique_ptr<crashpad::UserStreamDataSource, std::__1::default_delete<crashpad::UserStreamDataSource> > > > const*) + 4790 4 libdyld.dylib 0x00007fff675de015 start + 1 5 ??? 0x0000000000000008 0x0 + 8 [0614/033331.552454:ERROR:file_io.cc(89)] ReadExactly: expected 4, observed 0 [0614/033331.554027:ERROR:mach_extensions.cc(68)] bootstrap_check_in org.chromium.crashpad.child_port_handshake.76056.1075933.RYWTXCWPPKKJXJKX: unknown error code (141) [0614/033331.554392:FATAL:child_port_handshake.cc(111)] Check failed: server_port.is_valid(). 0 crashpad_handler 0x00000001034bd58c base::debug::StackTrace::StackTrace(unsigned long) + 28 1 crashpad_handler 0x00000001034aa3c1 logging::LogMessage::~LogMessage() + 225 2 crashpad_handler 0x00000001034c7274 crashpad::ChildPortHandshake::RunServerForFD(base::ScopedGeneric<int, base::internal::ScopedFDCloseTraits>, crashpad::ChildPortHandshake::PortRightType) + 516 3 crashpad_handler 0x0000000103499266 crashpad::HandlerMain(int, char**, std::__1::vector<std::__1::unique_ptr<crashpad::UserStreamDataSource, std::__1::default_delete<crashpad::UserStreamDataSource> >, std::__1::allocator<std::__1::unique_ptr<crashpad::UserStreamDataSource, std::__1::default_delete<crashpad::UserStreamDataSource> > > > const*) + 4790 4 libdyld.dylib 0x00007fff675de015 start + 1 5 ??? 0x0000000000000009 0x0 + 9
,
Jun 14 2018
There are failures with a similar crash stack on Mac 10.12: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.12%20Tests
,
Jun 14 2018
,
Jun 14 2018
,
Jun 14 2018
This isn't really crashpad-related. The system is hosed, and crashpad is just the first thing to notice in a fatal way. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 Deleted