DCHECK hit in cc::GpuImageDecodeCache::UnrefImageInternal: CalledOnValidSequence() |
||||
Issue descriptionChrome Version: ToT OS: Chrome OS What steps will reproduce the problem? (1) Build a dcheck_always_on=true build for link and deploy it to a link Chromebook. (2) Log in, do some activity for several seconds. What happens instead? [FATAL:ref_counted.h(95)] Check failed: CalledOnValidSequence(). #0 0x7fd086d39827 base::debug::StackTrace::StackTrace() #1 0x7fd086d5336d logging::LogMessage::~LogMessage() #2 0x7fd084bee3fd base::subtle::RefCountedBase::Release() #3 0x7fd087f0735a std::_Hashtable<>::_M_erase() #4 0x7fd087f0291c cc::GpuImageDecodeCache::UnrefImageInternal() #5 0x7fd087f04638 cc::GpuImageDecodeCache::DrawWithImageFinished() #6 0x7fd087f34e09 cc::ImageHijackCanvas::onDrawImageRect() #7 0x7fd0873eb137 SkCanvas::legacy_drawImageRect() #8 0x7fd08748d4ff _ZNK8SkRecord6Record5visitIRN9SkRecords4DrawEEEDTclfp_cvNS2_4NoOpE_EEEOT_ #9 0x7fd08748cd21 SkRecordDraw() #10 0x7fd08763482d SkBigPicture::playback() #11 0x7fd08781fa7e cc::(anonymous namespace)::RasterItem() #12 0x7fd08781f789 cc::DisplayItemList::Raster() #13 0x7fd087ee93af cc::RasterSource::RasterCommon() #14 0x7fd087ee8f46 cc::RasterSource::PlaybackToCanvas() #15 0x7fd087ee8cef cc::RasterSource::PlaybackToCanvas() #16 0x7fd087ee5d07 cc::GpuRasterBufferProvider::PlaybackOnWorkerThread() #17 0x7fd087ee58b6 cc::GpuRasterBufferProvider::RasterBufferImpl::Playback() #18 0x7fd087f224ea cc::(anonymous namespace)::RasterTaskImpl::RunOnWorkerThread() #19 0x7fd08a38fbc9 content::CategorizedWorkerPool::RunTaskInCategoryWithLockAcquired() #20 0x7fd08a38ec4c content::CategorizedWorkerPool::Run() #21 0x7fd086dae4de base::SimpleThread::ThreadMain() #22 0x7fd086da83ac base::(anonymous namespace)::ThreadFunc() #23 0x7fd083960558 <unknown> #24 0x7fd08268c08d clone ccameron@: PTAL. Assigning to you as your CL bdb2737223ac58596bffeb66a079dc6a80c3e5cc touched the GpuImageDecodeCache::UnrefImageInternal() recently; not sure whether that change could be related, but otherwise maybe you know whom to assign this to for triaging? Thanks.
,
May 25 2017
,
May 30 2017
We've switched to using RefCountedThreadSafe in this case (as of crrev.com/90567cc4853a3) so this should be fixed.
,
Aug 1 2017
,
Jan 22 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ccameron@chromium.org
, Apr 21 2017