Closed Bug 1242393 Opened 10 years ago Closed 10 years ago

crash in base::MessagePumpWin::RunWithDispatcher with Trusteer Rapport

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Version:
44 Branch
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox44 + fixed

People

(Reporter: philipp, Unassigned)

References

Details

(Keywords: crash)

Crash Data

[Tracking Requested - why for this release]: This bug was filed from the Socorro interface and is report bp-c0a793a6-b357-464a-92c2-516232160123. ============================================================= Crashing Thread (21) Frame Module Signature Source 0 @0xa464336b 1 @0x7160ffff 2 xul.dll base::MessagePumpWin::RunWithDispatcher(base::MessagePump::Delegate*, base::MessagePumpWin::Dispatcher*) ipc/chromium/src/base/message_pump_win.cc 3 xul.dll base::MessagePumpWin::Run(base::MessagePump::Delegate*) ipc/chromium/src/base/message_pump_win.h 4 xul.dll MessageLoop::RunHandler() ipc/chromium/src/base/message_loop.cc 5 kernelbase.dll InitializeCriticalSectionAndSpinCount the two signatures base::MessagePumpWin::RunWithDispatcher and NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run jumped up yesterday in 44 rc builds a bit and made up 1.5% of crashes. according to correlation data, those seem to be related to trusteer rapport on the affected systems: base::MessagePumpWin::RunWithDispatcher|EXCEPTION_ACCESS_VIOLATION_EXEC (132 crashes) 100% (132/132) vs. 4% (698/15841) TRF.dll (5.11.29.5) 100% (132/132) vs. 4% (698/15841) atl80.dll (8.0.50727.762) 100% (132/132) vs. 4% (698/15841) RapportUtil.dll 23% (30/132) vs. 1% (182/15841) 3.5.1507.105 77% (102/132) vs. 3% (516/15841) 3.5.1507.107 100% (132/132) vs. 4% (699/15841) rooksdol.dll (2.211.0.0) 100% (132/132) vs. 5% (762/15841) rooksbas.dll 0% (0/132) vs. 0% (1/15841) 2.106.0.0 0% (0/132) vs. 0% (1/15841) 2.107.0.0 100% (132/132) vs. 5% (760/15841) 2.143.0.0 99% (131/132) vs. 5% (714/15841) riched20.dll 0% (0/132) vs. 0% (1/15841) 5.30.23.1221 0% (0/132) vs. 0% (1/15841) 5.31.23.1228 4% (5/132) vs. 0% (39/15841) 5.31.23.1229 63% (83/132) vs. 3% (446/15841) 5.31.23.1230 33% (43/132) vs. 1% (227/15841) 5.31.23.1231 96% (127/132) vs. 4% (668/15841) RapportGP.DLL 21% (28/132) vs. 1% (177/15841) 3.5.1507.105 75% (99/132) vs. 3% (491/15841) 3.5.1507.107 96% (127/132) vs. 4% (668/15841) RapportTanzanEx440.DLL 21% (28/132) vs. 1% (177/15841) 3.5.1507.105 75% (99/132) vs. 3% (491/15841) 3.5.1507.107 NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run|EXCEPTION_ACCESS_VIOLATION_EXEC (98 crashes) 100% (98/98) vs. 4% (698/15841) TRF.dll (5.11.29.5) 100% (98/98) vs. 4% (698/15841) atl80.dll (8.0.50727.762) 100% (98/98) vs. 4% (698/15841) RapportUtil.dll 33% (32/98) vs. 1% (182/15841) 3.5.1507.105 67% (66/98) vs. 3% (516/15841) 3.5.1507.107 100% (98/98) vs. 4% (699/15841) rooksdol.dll (2.211.0.0) 100% (98/98) vs. 5% (762/15841) rooksbas.dll 0% (0/98) vs. 0% (1/15841) 2.106.0.0 0% (0/98) vs. 0% (1/15841) 2.107.0.0 100% (98/98) vs. 5% (760/15841) 2.143.0.0 99% (97/98) vs. 5% (714/15841) riched20.dll 0% (0/98) vs. 0% (1/15841) 5.30.23.1221 0% (0/98) vs. 0% (1/15841) 5.31.23.1228 7% (7/98) vs. 0% (39/15841) 5.31.23.1229 60% (59/98) vs. 3% (446/15841) 5.31.23.1230 32% (31/98) vs. 1% (227/15841) 5.31.23.1231 94% (92/98) vs. 4% (668/15841) RapportGP.DLL 33% (32/98) vs. 1% (177/15841) 3.5.1507.105 61% (60/98) vs. 3% (491/15841) 3.5.1507.107 94% (92/98) vs. 4% (668/15841) RapportTanzanEx440.DLL 33% (32/98) vs. 1% (177/15841) 3.5.1507.105 61% (60/98) vs. 3% (491/15841) 3.5.1507.107
Crash Signature: [@ base::MessagePumpWin::RunWithDispatcher] [@ NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run] → [@ base::MessagePumpWin::RunWithDispatcher] [@ NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run] [@ mozilla::ipc::MessagePump::Run]
can we do some outreach to ibm here as well - to get it on their radar at least?
Flags: needinfo?(sledru)
Crash Signature: [@ base::MessagePumpWin::RunWithDispatcher] [@ NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run] [@ mozilla::ipc::MessagePump::Run] → [@ base::MessagePumpWin::RunWithDispatcher] [@ NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run] [@ mozilla::ipc::MessagePump::Run] [@ base::MessagePumpForUI::DoRunLoop]
The bug 1235257 signatures are spiking as well.
They said "We released an update yesterday that should resolved most of the cases in FF44." I asked for a confirmation that this bug is fixed too.
Flags: needinfo?(sledru)
Philipp mentioned in #crashkill this morning that he can see the trusteer crashes going down in volume. Let's hope that the trend continues and trusteer related crashes are gone for Fx44.
due to the recent development in crash stats i'm going to mark this issue as fixed by trusteer's update: https://crash-stats.mozilla.com/signature/?date=%3E2016-01-15&signature=nsAppShell%3A%3AProcessNextNativeEvent#graphs
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox44: affected → fixed
Resolution: --- → FIXED
See Also: → 1303531
You need to log in before you can comment on or make changes to this bug.