Crash in mozglue.dll | mozilla::Telemetry::AccumulateTimeDelta
Categories
(Core :: mozglue, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | affected |
People
(Reporter: marcia, Unassigned)
Details
(Keywords: crash, regression)
Crash Data
This bug is for crash report bp-6b01e198-b3b4-4a50-a93f-9aa8e0190124.
Seen while looking at content crashes for 64.0.2: https://bit.ly/2Rc8qCY. Doesn't seem to be present in 66 or 65, nor in the 64.0 release. Comments mention repeatedly crashing. Filing since it is the #17 top content crash without a bug.
Top 10 frames of crashing thread:
0 mozglue.dll mozglue.dll@0x12797
1 xul.dll mozilla::Telemetry::AccumulateTimeDelta toolkit/components/telemetry/core/Telemetry.cpp:2021
2 xul.dll void nsRefreshDriver::Tick layout/base/nsRefreshDriver.cpp:2064
3 xul.dll void mozilla::RefreshDriverTimer::TickRefreshDrivers layout/base/nsRefreshDriver.cpp:300
4 xul.dll void mozilla::RefreshDriverTimer::Tick layout/base/nsRefreshDriver.cpp:318
5 xul.dll void mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::TickRefreshDriver layout/base/nsRefreshDriver.cpp:672
6 xul.dll mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::NotifyVsync layout/base/nsRefreshDriver.cpp:572
7 xul.dll mozilla::layout::VsyncChild::RecvNotify layout/ipc/VsyncChild.cpp:76
8 xul.dll mozilla::layout::PVsyncChild::OnMessageReceived ipc/ipdl/PVsyncChild.cpp:167
9 xul.dll void mozilla::ipc::MessageChannel::DispatchMessageW ipc/glue/MessageChannel.cpp:2182
|
Reporter | |
Comment 1•5 years ago
|
||
ni on Nathan - maybe he knows something since ht worked on the AccumulateTimeDelta part.
|
||
Comment 2•5 years ago
|
||
I don't know what's going on here; it's puzzling that mozglue doesn't have symbols. The telemetry code looks innocuous, so it must be something happening in mozglue, but we can't get a good picture of what's going on there.
The correlations look kinda weird:
(99.35% in signature vs 27.63% overall) platform_version = 10.0.17134 [100.0% vs 73.86% if platform_pretty_version = Windows 10]
(95.22% in signature vs 06.08% overall) Module "aticfx64.dll" = true
(95.22% in signature vs 06.12% overall) Module "atiuxp64.dll" = true
(95.22% in signature vs 06.40% overall) Module "atidxx64.dll" = true
(92.17% in signature vs 01.25% overall) adapter_driver_version_clean = 15.201.1151.0 [93.02% vs 48.20% if adapter_device_id = 0x9808]
(92.17% in signature vs 01.25% overall) adapter_driver_version = 15.201.1151.0 [41.31% vs 01.69% if startup_crash = null]
Almost exclusively on a certain version of Windows 10, almost exclusively on ATI cards, and almost exclusively on a particular driver version? That sound very strange.
Cornel, is it possible for someone to try and reproduce this?
|
||
Comment 3•5 years ago
|
||
We're currently investigating this matter and we'll follow-up with our results early next week.
Leaving the ni? in place until then.
|
||
Comment 4•5 years ago
|
||
I've performed exploratory testing on Firefox 64.0.2 and on Firefox 65.0 without being able to reproduce the crash.
I used all the links form the comments found in the crash report and a few other top sites.
The tests were performed under Windows 10x64 with AMD Radeon HD 7700 and Intel HD 2500 GPU.
Please let me know if I can help any further with the investigation.
|
||
Updated•5 years ago
|
|
||
Comment 5•5 years ago
|
||
the crashes are gone again in 65.0. they were all coming from the known buggy amd cpu "family 20 model 2" which is exhibiting build-specific crashing issues every now and then.
Description
•