Closed Bug 1435510 Opened 2 years ago Closed 2 years ago

IBM Trusteer Rapport causing crashes

Categories

(External Software Affecting Firefox :: Other, defect, critical)

x86_64
Windows
defect
Not set
critical

Tracking

(firefox58+ unaffected, firefox59+ unaffected)

RESOLVED WORKSFORME
Tracking Status
firefox58 + unaffected
firefox59 + unaffected

People

(Reporter: philipp, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is
report bp-b8ac2b07-0c1a-4b36-bfeb-969c10180203.
=============================================================

a number of crash signatures are spiking up since thursday 2018-02-01, all with involvement of modules relating to trusteer rapport, so probably an update of theirs is causing stability issues again.
Jimm or maybe Adam, would either of you like to write to the Trusteer team? This is a very high volume crash for release 58.
Flags: needinfo?(jmathies)
Flags: needinfo?(astevenson)
Tracking for 58 and 59 releases.
I've contacted them via email. They are usually responsive.
Flags: needinfo?(jmathies)
Flags: needinfo?(astevenson)
Thanks Marco! We have a mailing list as well (if needed).
Windows 10 is particularly affected.

(In reply to Adam Stevenson [:adamopenweb] from comment #4)
> Thanks Marco! We have a mailing list as well (if needed).

Thanks, I've sent the email to the mailing list too.
Summary: IBM Trusteer Rapport update causing havoc again → IBM Trusteer Rapport causing crashes
I've got a reply from Trusteer. They hadn't noticed the crash because it was not showing up on their telemetry, but have managed to track down the problem and released a fix. We should monitor the crash rate and hopefully see a reduction very soon.

For the future, they are going to switch to an extension, so hopefully they won't be able to crash the browser anymore.
the crash volume is going down significantly yesterday & today, so the issue seems to have got successfully fixed by the third-party.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.