Closed
Bug 864912
Opened 11 years ago
Closed 10 years ago
startup crash in mozilla::layers::CrossProcessCompositorParent::AllocPLayers
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox22 | --- | unaffected |
firefox23 | --- | affected |
People
(Reporter: scoobidiver, Unassigned)
Details
(Keywords: crash, regression, reproducible, Whiteboard: [startupcrash])
Crash Data
It's a regression that first showed up in 23.0a1/20130421. A comment says: "browser.tabs.remote = true". Signature mozilla::layers::CrossProcessCompositorParent::AllocPLayers(mozilla::layers::LayersBackend const&, unsigned __int64 const&, mozilla::layers::TextureFactoryIdentifier*) More Reports Search UUID 89ff829b-cc30-4ade-94d1-ced952130423 Date Processed 2013-04-23 18:07:41 Uptime 4 Last Crash 6 seconds before submission Install Age 3.0 minutes since version was first installed. Install Time 2013-04-23 18:04:27 Product Firefox Version 23.0a1 Build ID 20130423030935 Release Channel nightly OS Windows NT OS Version 5.1.2600 Service Pack 3 Build Architecture x86 Build Architecture Info GenuineIntel family 6 model 23 stepping 6 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x158 App Notes AdapterVendorID: 0x10de, AdapterDeviceID: 0x0e22, AdapterSubsysID: 00000000, AdapterDriverVersion: 6.14.12.9610 D3D10 Layers? D3D10 Layers- D3D9 Layers? D3D9 Layers+ Processor Notes sp-processor07.phx1.mozilla.com_31665:2012; exploitability tool failed: 127 EMCheckCompatibility False Adapter Vendor ID 0x10de Adapter Device ID 0x0e22 Total Virtual Memory 2147352576 Available Virtual Memory 1885188096 System Memory Use Percentage 24 Available Page File 4646735872 Available Physical Memory 2535133184 Frame Module Signature Source 0 xul.dll mozilla::layers::CrossProcessCompositorParent::AllocPLayers gfx/layers/ipc/CompositorParent.cpp:1374 1 xul.dll mozilla::layers::PCompositorParent::OnMessageReceived obj-firefox/ipc/ipdl/PCompositorParent.cpp:546 2 xul.dll mozilla::ipc::SyncChannel::OnDispatchMessage ipc/glue/SyncChannel.cpp:145 3 xul.dll mozilla::ipc::RPCChannel::OnMaybeDequeueOne ipc/glue/RPCChannel.cpp:400 4 xul.dll MessageLoop::RunTask ipc/chromium/src/base/message_loop.cc:337 5 xul.dll MessageLoop::DeferOrRunPendingTask ipc/chromium/src/base/message_loop.cc:345 6 xul.dll MessageLoop::DoWork ipc/chromium/src/base/message_loop.cc:445 7 xul.dll base::MessagePumpDefault::Run ipc/chromium/src/base/message_pump_default.cc:23 8 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:212 9 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:186 10 xul.dll base::Thread::ThreadMain ipc/chromium/src/base/thread.cc:159 11 xul.dll `anonymous namespace'::ThreadFunc ipc/chromium/src/base/platform_thread_win.cc:26 12 kernel32.dll BaseThreadStart More reports at: https://crash-stats.mozilla.com/report/list?signature=mozilla%3A%3Alayers%3A%3ACrossProcessCompositorParent%3A%3AAllocPLayers%28mozilla%3A%3Alayers%3A%3ALayersBackend+const%26%2C+unsigned+__int64+const%26%2C+mozilla%3A%3Alayers%3A%3ATextureFactoryIdentifier*%29
It's easily reproducible: Create the boolean browser.tabs.remote = true and open any webpage to crash FF23. Regression range: m-c good=2013-04-10 bad=2013-04-11 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9db46ddfb517&tochange=2949e808ed33 My guess it regressed by: Bas Schouten — Bug 825928: Land layers refactoring
Keywords: reproducible
The tabs.remote pref has only been around since 4-22/23 (bug 862078) and isn't intended to be usable yet, AIUI.
Reporter | ||
Updated•11 years ago
|
Crash Signature: [@ mozilla::layers::CrossProcessCompositorParent::AllocPLayers(mozilla::layers::LayersBackend const&, unsigned __int64 const&, mozilla::layers::TextureFactoryIdentifier*)] → [@ mozilla::layers::CrossProcessCompositorParent::AllocPLayers(mozilla::layers::LayersBackend const&, unsigned __int64 const&, mozilla::layers::TextureFactoryIdentifier*)]
[@ mozilla::layers::CrossProcessCompositorParent::AllocPLayerTransaction(mozilla::…
Reporter | ||
Updated•11 years ago
|
Crash Signature: , mozilla::layers::TextureFactoryIdentifier*)]
[@ mozilla::layers::CrossProcessCompositorParent::AllocPLayerTransaction(mozilla::layers::LayersBackend const&, unsigned __int64 const&, mozilla::layers::TextureFactoryIdentifier*)] → , mozilla::layers::TextureFactoryIdentifier*)]
[@ mozilla::layers::CrossProcessCompositorParent::AllocPLayerTransaction(mozilla::layers::LayersBackend const&, unsigned __int64 const&, mozilla::layers::TextureFactoryIdentifier*)]
[@ mozilla::layers::Cros…
Comment 3•10 years ago
|
||
small but significant sample of crash-stats have no reports for any version on crash-stats, in two 2 week periods, for any signature containing mozilla::layers::CrossProcessCompositorParent::AllocPLayers There are some for mozilla::layers::CrossProcessCompositorParent::ForceComposite, but less than 10 per version per 4 week period. https://crash-stats.mozilla.com/report/list?signature=mozilla%3A%3Alayers%3A%3ACrossProcessCompositorParent%3A%3AForceComposite%28mozilla%3A%3Alayers%3A%3ALayerTransactionParent*%29&product=Firefox&query_type=contains&range_unit=weeks&process_type=any&hang_type=any&date=2014-10-26+22%3A00%3A00&range_value=2#tab-reports
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Comment 4•10 years ago
|
||
(and none of the mozilla::layers::CrossProcessCompositorParent::ForceComposite are startup)
Summary: crash in mozilla::layers::CrossProcessCompositorParent::AllocPLayers → startup crash in mozilla::layers::CrossProcessCompositorParent::AllocPLayers
You need to log in
before you can comment on or make changes to this bug.
Description
•