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

Issue 738851 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Crash in cc::ResourceProvider::CreateBitmap due to shared_bitmap_manager_ being NULL

Reported by gevorgvo...@cloud.upwork.com, Jul 3 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0

Steps to reproduce the problem:
N/A

What is the expected behavior?

What went wrong?
We received a crash report on our app that is written on top of Electron. This is the stack trace:

 	KERNELBASE.dll!_RaiseException@16()	Unknown
	upwork.exe!cc::ResourceProvider::CreateBitmap(const gfx::Size & size, const gfx::ColorSpace & color_space) Line 645	C++
 	upwork.exe!cc::ResourceProvider::CreateResource(const gfx::Size & size, cc::ResourceProvider::TextureHint hint, cc::ResourceFormat format, const gfx::ColorSpace & color_space) Line 587	C++
 	upwork.exe!cc::ScopedResource::Allocate(const gfx::Size & size, cc::ResourceProvider::TextureHint hint, cc::ResourceFormat format, const gfx::ColorSpace & color_space) Line 26	C++
 	upwork.exe!cc::ResourcePool::CreateResource(const gfx::Size & size, cc::ResourceFormat format, const gfx::ColorSpace & color_space) Line 141	C++
 	upwork.exe!cc::ResourcePool::AcquireResource(const gfx::Size & size, cc::ResourceFormat format, const gfx::ColorSpace & color_space) Line 165	C++
 	upwork.exe!cc::TileManager::CreateRasterTask(const cc::PrioritizedTile & prioritized_tile, const gfx::ColorSpace & color_space) Line 984	C++
 	upwork.exe!cc::TileManager::ScheduleTasks(const cc::TileManager::PrioritizedWorkToSchedule & work_to_schedule) Line 849	C++
 	upwork.exe!cc::TileManager::PrepareTiles(const cc::GlobalStateThatImpactsTilePriority & state) Line 529	C++
 	upwork.exe!cc::LayerTreeHostImpl::PrepareTiles() Line 490	C++
 	upwork.exe!cc::LayerTreeHostImpl::CommitComplete() Line 362	C++
 	upwork.exe!cc::ProxyImpl::ScheduledActionCommit() Line 505	C++
 	upwork.exe!cc::Scheduler::ProcessScheduledActions() Line 599	C++
 	upwork.exe!cc::Scheduler::NotifyReadyToCommit() Line 162	C++
 	upwork.exe!cc::ProxyImpl::NotifyReadyToCommitOnImpl(cc::CompletionEvent * completion, cc::LayerTreeHostInProcess * layer_tree_host, base::TimeTicks main_thread_start_time, bool hold_commit_for_activation) Line 253	C++
 	upwork.exe!base::internal::Invoker<base::internal::BindState<void (__thiscall cc::ProxyImpl::*)(cc::CompletionEvent *,cc::LayerTreeHostInProcess *,base::TimeTicks,bool),base::WeakPtr<cc::ProxyImpl>,cc::CompletionEvent *,cc::LayerTreeHostInProcess *,base::TimeTicks,bool>,void __cdecl(void)>::Run(base::internal::BindStateBase * base) Line 339	C++
 	[External Code]

What could be the underlying cause? Is it possible to check shared_bitmap_manager_ against NULL in ResourceProvider::CreateBitmap() to avoid the crash?

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 10.0
Flash Version: N/A
 
Components: -Blink Internals>Compositing

Comment 2 by enne@chromium.org, Jul 7 2017

Cc: danakj@chromium.org jbau...@chromium.org
Status: Available (was: Unconfirmed)
A shared bitmap manager needs to be present when you're not using GL compositing. CreateBitmap() is used when not using GL compositing. It sounds like something isn't being set up correctly in your app or in Electron.

This is where teh shared_bitmap_manager is coming from in ToT chromium: https://cs.chromium.org/chromium/src/content/renderer/render_thread_impl.cc?rcl=b9a2a9b60034d3ee2138c4815bc3c66b13cee3b5&l=2009
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 9

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Archived (was: Untriaged)
This code is gone

Sign in to add a comment