New issue
Advanced search Search tips

Issue 604652 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Apr 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

FATAL:rand_util_posix.cc(54)] Check failed

Reported by markustr...@gmail.com, Apr 19 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2713.0 Safari/537.36

Steps to reproduce the problem:
Chromium hits the assertion in base/rand_util_posix.cc:54

What is the expected behavior?

What went wrong?
[23620:23620:0419/105518:FATAL:rand_util_posix.cc(54)] Check failed: success. 
#0 0x555556474a2e base::debug::StackTrace::StackTrace()
#1 0x55555648b0e7 logging::LogMessage::~LogMessage()
#2 0x5555564a7d4c base::RandBytes()
#3 0x555557029feb mojo::edk::NodeController::NodeController()
#4 0x55555701f928 mojo::edk::Core::GetNodeController()
#5 0x55555701f985 mojo::edk::Core::SetIOTaskRunner()
#6 0x55555701e732 mojo::edk::InitIPCSupport()
#7 0x55555a78def1 IPC::(anonymous namespace)::IPCSupportInitializer::Init()
#8 0x55555a78dff8 IPC::ScopedIPCSupport::ScopedIPCSupport()
#9 0x55555acd561c content::ChildThreadImpl::Init()
#10 0x555559799b88 content::RenderThreadImpl::RenderThreadImpl()
#11 0x555559799fbf content::RenderThreadImpl::Create()
#12 0x5555597bd50d content::RendererMain()
#13 0x5555564445e3 content::ContentMainRunnerImpl::Run()
#14 0x555556443c6c content::ContentMain()
#15 0x555556029fdd ChromeMain
#16 0x7ffff601af11 __libc_start_main
#17 0x555556029e5a _start

This issue started with 51.0 and still happens in 52.0

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? Yes 50.0 is fine

Chrome version: 52.0.2713.0  Channel: n/a
OS Version: 
Flash Version:
 
Labels: Te-NeedsFurtherTriage
Looks like the issue is caused by a header change in glibc trunk.

Building Chromium with glibc-2.23 "fixes" the issue. 
Running official Chrome from the Dev channel works fine even with glibc trunk.
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 25 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment