What could cause GrOpsTask::recordOp crash?

26 views
Skip to first unread message

Jona

unread,
Aug 28, 2021, 1:13:15 PMAug 28
to skia-discuss
Currently my app is published on Google Play and the top reported crash has to do with Skia. I'm sure there is something I'm doing that is causing this issue. I would love to get anyones input into potential causes and where I could start looking to resolve this issue.

This happens on both ARM and ARM64 bit processors.

CRASH:
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
Hide crash
GrOpsTask::recordOp(std::__ndk1::unique_ptr<GrOp, std::__ndk1::default_delete<GrOp> >, GrProcessorSet::Analysis, GrAppliedClip*, GrXferProcessor::DstProxyView const*, GrCaps const&)

CRASH STACK
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> com.vblast.flipaclip <<<

backtrace:
  #00  pc 0000000000c49fa0  /data/app/{apppackage}==/lib/arm64/libfc.so (GrOpsTask::recordOp(std::__ndk1::unique_ptr<GrOp, std::__ndk1::default_delete<GrOp> >, GrProcessorSet::Analysis, GrAppliedClip*, GrXferProcessor::DstProxyView const*, GrCaps const&)) (SourceCode: GrOpsTask.cpp)

Jona

unread,
Aug 28, 2021, 1:14:59 PMAug 28
to skia-discuss
Oh I'm on Skia m92.

Jona

unread,
Sep 9, 2021, 4:54:37 PMSep 9
to skia-discuss
In regards to this crash, I'm thinking maybe that the static skia library doesn't have any symbols for me to get more information?

Anyone know if the static skia library includes the symbols when building with "is_official_build=true is_debug=false"?

I'm in the process now of testing if building it with "is_official_build=false is_debug=true" helps with the crash stacks.
Reply all
Reply to author
Forward
0 new messages