Closed
Bug 704664
Opened 13 years ago
Closed 13 years ago
Login crashes with Firefox 9 on Nordea online banking (popular Scandinavian bank)
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 702111
People
(Reporter: cww, Unassigned)
Details
(Keywords: crash, stackwanted)
From input:
http://input.mozilla.com/en-US/opinion/2532561
http://input.mozilla.com/en-US/opinion/2531644
http://input.mozilla.com/en-US/opinion/2529562
http://input.mozilla.com/en-US/opinion/2527829
http://input.mozilla.com/en-US/opinion/2522893
http://input.mozilla.com/en-US/opinion/2520666
http://input.mozilla.com/en-US/opinion/2516813
Looks like users are crashing when trying to log in. Pulled from input -- I don't have a way to reproduce.
Comment 1•13 years ago
|
||
We need crash IDs.....
Maybe Kairo can search with the URL to find the reports if there are any..
Severity: normal → critical
Keywords: crash,
stackwanted
Comment 2•13 years ago
|
||
Could you please give us the URL to even search for? I can surely try to grep our CSVs for an URL but I need to know what to grep for.
Comment 4•13 years ago
|
||
E.g. https://solo1.nordea.fi/nsp/engine?language=en&country=fi is Nordea's Finnish netbank site in English. But it crashes later during the session, after a succesful logon. The input comments are not that clear about the actual crashiness.
For me Nordea does not fully crash Firefox 10.0a2, but instead the bank's server detects some connection breakage and gives an internal error message. English version:
"System error
A system error has occurred in the service and your Netbank session has been closed. Unsaved information may have been lost. Please log in again to Netbank."
See https://bugzilla.mozilla.org/show_bug.cgi?id=702111#c14 and https://bugzilla.mozilla.org/show_bug.cgi?id=702111#c20
Comment 5•13 years ago
|
||
Beta 9.0b5 (Firefox/9.0 ID:20111206234556) seems to work with Nordea. That beta contains the temporary fix for the issue discussed here:
https://bugzilla.mozilla.org/show_bug.cgi?id=702111#c23
So, this apparently is the consequence of the same issue.
Comment 6•13 years ago
|
||
In that case, let's mark it as that.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•