Mozilla support will not let me sign in. I can log in to my mozilla account in a separate window, but not on the support site.
I have repeatedly tried to log in to support, because mozilla is crashing repeatedly, but I can't log in to the support site. I even tried requesting a password reset from that site, repeatedly, but the password reset email from mozilla is never received. Why can I log in to my regular mozilla account, but not the support site?
Ausgewählte Lösung
Ok I see more info. You jumped in to someone else's question thread
bp-e032d320-68cc-4a9e-ab9a-38b802150527 5/27/2015 9:16 AM bp-3f63de39-39e3-43fa-9428-b813b2150527 5/26/2015 9:59 PM bp-f620d88a-5136-4e02-9449-c573c2150526 5/26/2015 3:22 PM bp-2d9f51c0-3743-4679-a548-10d5e2150525 5/25/2015 4:04 PM bp-629a967e-7ded-4bc8-8dbf-5632b2150524 5/24/2015 6:28 PM bp-96c7fb8a-93df-4955-91eb-6b69e2150524 5/24/2015 5:35 PM
philipp said
james, can you use firefox beta and see if the crashes continue: https://www.mozilla.org/firefox/beta/
I understand you to be saying the Crashes have stopped but Firefox is very slow.
- Do things improve if you re-enable Hardware Acceleration (HWA)
- Or do crashes come back with hardware acceleration back on ?
(The graphics driver update my allow HWA to work again.)
Can you describe what you mean by slow and what you see e.g.
- Is it only video or pages with intensive graphics or animations that are affected ?
- How bad is this, does the display stutter slightly, page scrolling is slow, or the whole browser freezes:
- How long for less than a second, more than 3|10|30 seconds
For forum cross referencing purposes
- Your Reports for CrashIDs bp-e032d320-68cc-4a9e-ab9a-38b802150527
... bp- 96c7fb8a-93df-4955-91eb-6b69e2150524 - Crash Signature: js::frontend::Parser<js::frontend::SyntaxParseHandler>::unaryExpr(js::frontend::Parser<js::frontend::SyntaxParseHandler>::InvokedPrediction)
- Related bug 1159973
Alle Antworten (4)
Sorry I do not understand your problem. This post and thread is on the mozilla support site.
You must be or have been logged in as you have successfully posted.
Are you trying to use another third party site such as mozillazinie ( mozillazine.org ) ?
Or are you having trouble with Firefox Sync and its account ? Firefox Sync troubleshooting and tips
I am biting my tongue at your response, but, yes, I was finally able to log in, after numerous attempts. As *Philipp* suggested, I have upgraded to Firefox Beta, disabled hardware acceleration, and updated my Intel graphics driver. No improvement whatsoever - Firefox is still agonizingly slow.
I take that back - no *crashes* since I installed Firefox Beta, but it is very, very slow.
Ausgewählte Lösung
Ok I see more info. You jumped in to someone else's question thread
bp-e032d320-68cc-4a9e-ab9a-38b802150527 5/27/2015 9:16 AM bp-3f63de39-39e3-43fa-9428-b813b2150527 5/26/2015 9:59 PM bp-f620d88a-5136-4e02-9449-c573c2150526 5/26/2015 3:22 PM bp-2d9f51c0-3743-4679-a548-10d5e2150525 5/25/2015 4:04 PM bp-629a967e-7ded-4bc8-8dbf-5632b2150524 5/24/2015 6:28 PM bp-96c7fb8a-93df-4955-91eb-6b69e2150524 5/24/2015 5:35 PM
philipp said
james, can you use firefox beta and see if the crashes continue: https://www.mozilla.org/firefox/beta/
I understand you to be saying the Crashes have stopped but Firefox is very slow.
- Do things improve if you re-enable Hardware Acceleration (HWA)
- Or do crashes come back with hardware acceleration back on ?
(The graphics driver update my allow HWA to work again.)
Can you describe what you mean by slow and what you see e.g.
- Is it only video or pages with intensive graphics or animations that are affected ?
- How bad is this, does the display stutter slightly, page scrolling is slow, or the whole browser freezes:
- How long for less than a second, more than 3|10|30 seconds
For forum cross referencing purposes
- Your Reports for CrashIDs bp-e032d320-68cc-4a9e-ab9a-38b802150527
... bp- 96c7fb8a-93df-4955-91eb-6b69e2150524 - Crash Signature: js::frontend::Parser<js::frontend::SyntaxParseHandler>::unaryExpr(js::frontend::Parser<js::frontend::SyntaxParseHandler>::InvokedPrediction)
- Related bug 1159973