New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 702950 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in [vdso]

Project Member Reported by ClusterFuzz, Mar 19 2017

Issue description

Cc: ananta@chromium.org yhirano@chromium.org scottmg@chromium.org
Components: Internals>Network
Labels: Test-Predator-Wrong
Predator and regressing range did not given any suspected CL. could someone please take a look?.
Thank you.
A unreproducible crash in a one-line function (that doesn't appear to have any syscalls) in a VDSO...I'm unsure how to start investigating.

I find this GN config weird:
target_cpu = "x86"
v8_target_cpu = "arm"
I'm redoing the task for clarity. I think [vdso] is a red herring due to clusterfuzz instrumentation (though I'm not sure *why*). I see it also in  issue 708438  which is a real crasher. 

That being said, it not being reproducible is not a great sign.
Looking at the error, I think it is likely that this is crashing accessing network_delegate_, which is at 32 byte offset (0x20) from URLRequestContext. It is also unclear that this object will always be non-null.

I couldn't find any crashers on the dashboard though. Maybe we should add a CHECK?
Mergedinto: 624888
Status: Duplicate (was: Untriaged)
Hey whadayaknow, this is a dupe of issue 624888

Sign in to add a comment