Closed Bug 985428 Opened 10 years ago Closed 7 years ago

crashes in rapporttanzan28.dll (Trusteer Rapport)

Categories

(Firefox :: Extension Compatibility, defect)

x86
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox28 + affected

People

(Reporter: kairo, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, topcrash-win)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-597602c5-e79d-4f6f-a3e2-16c422140319.
=============================================================

Since the Firefox 28.0 release yesterday, we have a high frequency of crashes in rapporttanzan28.dll, I see three different signatures, i.e. locations in the DLL where those crashes happen:

https://crash-stats.mozilla.com/report/list?signature=rapporttanzan28.dll%400x1ea2e
https://crash-stats.mozilla.com/report/list?signature=rapporttanzan28.dll%400x1ea0e
https://crash-stats.mozilla.com/report/list?signature=rapporttanzan28.dll%400xabef

I'm CCing ilan.fraiman@trusteer who has been reacting quite fast on previous reports of this kind, see bug 814096 and bug 806174.

Also requesting tracking for 28 to get it on the radar of our release managers. The @0x1ea2e signature is currently the #1 crash in early 28 release data.
Keywords: topcrash-win
Thank you. We are on it and will update once we have more information.
We found the problem and started an update of our users population. The fix will start to reach the clients in the next few hours.
This crash is caused by my computer.
Since my system with Win 7 has a problem that some system environmental variables such as 
windir and systemroot are missing at some start-up points.  With the safe mode, firefox works.
Firefox crashes when it tries to request the master password. 

I think that the module that asks the master password has changed that 28.0 uses environmental
variables while the previous version used the direct path without using environmental variables.
In case of using environmental variables, please check whether the variables are actually defined.

Hope that this will help the debugging.

- Gitchang -
(In reply to ilan.fraiman from comment #2)
> We found the problem and started an update of our users population. The fix
> will start to reach the clients in the next few hours.

Thanks, that's awesome to hear - and really great reaction time! :)
Will mark affected (and tracking for now) until we get updates that this is going down.  +1 on the thanks for rapid response - much appreciated!
The crashes have been very much reduced in rate in the last 12h or so, and seem to continue to decline, looks like the awesomely fast fix from Trusteer really works!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.