New issue
Advanced search Search tips

Issue 764137 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 764327
Owner: ----
Closed: Sep 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug



Sign in to add a comment

[crash] Awe, snap at startup

Project Member Reported by dschuyler@chromium.org, Sep 12 2017

Issue description

Get chromium code as of 03b75bcf15d44dcf98b02301bef21222afdf0346

The code will build and run, but is not usable for development. All URLs (that I've tried) result in an Awe, Snap page.


#
# Fatal error in ../../v8/src/snapshot/snapshot.h, line 31
# Check failed: IsSane().
#
#0 0x7f151981ec87 base::debug::StackTrace::StackTrace()
#1 0x7f1514d50cd5 gin::(anonymous namespace)::PrintStackTrace()
#2 0x7f150adf68dc V8_Fatal()
#3 0x7f1514a5a693 v8::internal::SnapshotData::SnapshotData()
#4 0x7f1514a5a2cb v8::internal::Snapshot::Initialize()
#5 0x7f15144a2746 v8::IsolateNewImpl()
#6 0x7f1514d46647 gin::IsolateHolder::IsolateHolder()
#7 0x7f151265ce3a blink::V8PerIsolateData::V8PerIsolateData()
#8 0x7f151265d93e blink::V8PerIsolateData::Initialize()
#9 0x7f1513280fed blink::V8Initializer::InitializeMainThread()
#10 0x7f150d4edd5d blink::Initialize()
#11 0x7f151776988a content::RenderThreadImpl::InitializeWebKit()
#12 0x7f15177674cf content::RenderThreadImpl::Init()
#13 0x7f1517766865 content::RenderThreadImpl::RenderThreadImpl()
#14 0x7f15177663d9 content::RenderThreadImpl::Create()
#15 0x7f1517793bc4 content::RendererMain()
#16 0x7f151789b832 content::RunZygote()
#17 0x7f151789ca51 content::ContentMainRunnerImpl::Run()
#18 0x7f1519d3ed8d service_manager::Main()
#19 0x7f151789b582 content::ContentMain()
#20 0x5564d89626b4 ChromeMain
#21 0x7f150e6f9f45 __libc_start_main
#22 0x5564d896250f <unknown>
Received signal 4 ILL_ILLOPN 7f150adf7e1f
Received signal 11 SEGV_MAPERR 003000000020
[115763:115763:0911/165645.505339:INFO:chrome_cryptauth_service.cc(222)] Profile is not authenticated yet; waiting before starting CryptAuth managers.

 
Status: WontFix (was: Untriaged)
This can be resolve by removing all old output from the build directory. i.e. it seems that some prior build cruft in the out directory was the issue.

Closing this since it has a simple workaround.
I got this when I synced from r500514 to r501501. I clobbered my .bin files and all is good again.
Mergedinto: 764327
Status: Duplicate (was: WontFix)

Sign in to add a comment