[:philipp] Reporter
	Description • 7 years ago

This bug was filed from the Socorro interface and is 
report bp-a59bec36-9b1a-42b1-bf60-a01fb0171104.
=============================================================
Crashing Thread (22), Name: Compositor
Frame 	Module 	Signature 	Source
0 	xul.dll 	gfxFontFaceBufferSource::Release() 	gfx/thebes/gfxUserFontSet.h:31
1 	xul.dll 	mozilla::layers::LayerMLGPU::PrepareToRender(mozilla::layers::FrameBuilder*, mozilla::gfx::IntRectTyped<mozilla::RenderTargetPixel> const&) 	gfx/layers/mlgpu/LayerMLGPU.cpp:57
2 	xul.dll 	mozilla::layers::FrameBuilder::ProcessContainerLayer(mozilla::layers::ContainerLayer*, mozilla::layers::RenderViewMLGPU*, mozilla::gfx::IntRectTyped<mozilla::RenderTargetPixel> const&, mozilla::Maybe<mozilla::gfx::PolygonTyped<mozilla::gfx::UnknownUnits> >&) 	gfx/layers/mlgpu/FrameBuilder.cpp:161
3 	xul.dll 	mozilla::layers::FrameBuilder::AssignLayer(mozilla::layers::Layer*, mozilla::layers::RenderViewMLGPU*, mozilla::gfx::IntRectTyped<mozilla::RenderTargetPixel> const&, mozilla::Maybe<mozilla::gfx::PolygonTyped<mozilla::gfx::UnknownUnits> >&&) 	gfx/layers/mlgpu/FrameBuilder.cpp:122
4 	xul.dll 	mozilla::layers::FrameBuilder::ProcessChildList(mozilla::layers::ContainerLayer*, mozilla::layers::RenderViewMLGPU*, mozilla::gfx::IntRectTyped<mozilla::RenderTargetPixel> const&, mozilla::Maybe<mozilla::gfx::PolygonTyped<mozilla::gfx::UnknownUnits> > const&) 	gfx/layers/mlgpu/FrameBuilder.cpp:228
5 	xul.dll 	mozilla::layers::FrameBuilder::ProcessContainerLayer(mozilla::layers::ContainerLayer*, mozilla::layers::RenderViewMLGPU*, mozilla::gfx::IntRectTyped<mozilla::RenderTargetPixel> const&, mozilla::Maybe<mozilla::gfx::PolygonTyped<mozilla::gfx::UnknownUnits> >&) 	gfx/layers/mlgpu/FrameBuilder.cpp:172
6 	xul.dll 	mozilla::layers::FrameBuilder::AssignLayer(mozilla::layers::Layer*, mozilla::layers::RenderViewMLGPU*, mozilla::gfx::IntRectTyped<mozilla::RenderTargetPixel> const&, mozilla::Maybe<mozilla::gfx::PolygonTyped<mozilla::gfx::UnknownUnits> >&&) 	gfx/layers/mlgpu/FrameBuilder.cpp:122
7 	xul.dll 	mozilla::layers::FrameBuilder::Build() 	gfx/layers/mlgpu/FrameBuilder.cpp:72
8 	xul.dll 	mozilla::layers::LayerManagerMLGPU::RenderLayers() 	gfx/layers/mlgpu/LayerManagerMLGPU.cpp:364
9 	xul.dll 	mozilla::layers::LayerManagerMLGPU::Composite() 	gfx/layers/mlgpu/LayerManagerMLGPU.cpp:320
10 	xul.dll 	mozilla::layers::LayerManagerMLGPU::EndTransaction(mozilla::TimeStamp const&, mozilla::layers::LayerManager::EndTransactionFlags) 	gfx/layers/mlgpu/LayerManagerMLGPU.cpp:279
11 	xul.dll 	mozilla::layers::CompositorBridgeParent::CompositeToTarget(mozilla::gfx::DrawTarget*, mozilla::gfx::IntRectTyped<mozilla::gfx::UnknownUnits> const*) 	gfx/layers/ipc/CompositorBridgeParent.cpp:1041
12 	xul.dll 	mozilla::layers::CompositorVsyncScheduler::Composite(mozilla::TimeStamp) 	gfx/layers/ipc/CompositorVsyncScheduler.cpp:262
13 	xul.dll 	mozilla::detail::RunnableMethodImpl<mozilla::layers::CompositorVsyncScheduler* const, void ( mozilla::layers::CompositorVsyncScheduler::*)(mozilla::TimeStamp), 1, 1, mozilla::TimeStamp>::Run() 	xpcom/threads/nsThreadUtils.h:1192
14 	xul.dll 	MessageLoop::DoWork() 	ipc/chromium/src/base/message_loop.cc:535
15 	xul.dll 	base::MessagePumpForUI::DoRunLoop() 	ipc/chromium/src/base/message_pump_win.cc:210
16 	xul.dll 	base::MessagePumpWin::Run(base::MessagePump::Delegate*) 	ipc/chromium/src/base/message_pump_win.h:80
17 	xul.dll 	MessageLoop::RunHandler() 	ipc/chromium/src/base/message_loop.cc:319
18 	xul.dll 	MessageLoop::Run() 	ipc/chromium/src/base/message_loop.cc:299
19 	xul.dll 	base::Thread::ThreadMain() 	ipc/chromium/src/base/thread.cc:181
20 	xul.dll 	`anonymous namespace'::ThreadFunc 	ipc/chromium/src/base/platform_thread_win.cc:28
21 	kernel32.dll 	BaseThreadInitThunk 	
22 	ntdll.dll 	RtlUserThreadStart 	
23 	kernel32.dll 	BasepReportFault 	
24 	kernel32.dll 	BasepReportFault

this signature is starting to appear more frequently in the 57.0b cycle - first in beta 3 and then again in beta 12 and subsequent builds. it's mainly affecting windows 7 installations, ther is no correlation with particular gpus though.

	Peter Chang[:pchang]
	Comment 1 • 7 years ago

From the call stack, I didn't see the relation between frame 0 (gfxFontFaceBufferSource::Release) and 1(LayerMLGPU::PrepareToRender). David, do you think this was related to Font or MLGPU only?

	David Anderson [:dvander] - inactive, e-mail if emergency
	Comment 2 • 7 years ago

Indeed something is wrong with the stack there. This looks like bug 1407283 with a new signature.