Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

FF18 Mobile crashes

  • 4 respostas
  • 3 têm este problema
  • 8 visualizações
  • Última resposta por tibitts

tibitts
tibitts
more options

FF18 for Android on a Nexus S, 512 MB RAM, Jelly Bean 4.1.2, no Flash installed, Sync is set up

A number of sites which used to work with FF17 now crash with FF18. Examples: http://www.williamsf1.com/home https://groups.google.com/group/mozilla.support.firefox/topics?lnk=srg FF just closes, no crash dump is created. Sometimes (not always) FF does not open properly after a crash. I.e. it opens a blank page with no content at all, no tabs, it just hangs and has to be closed. The next attempt to start it is then successful. Is anyone else seeing this? If so, are there open bugs? Another example where FF18 crashes, but I can't tell whether this worked with v17 before. http://www.dakar.com/index_DAKus.html Overall FF18 Mobile is a disappointment and a step backwards for me. Thanks.

FF18 for Android on a Nexus S, 512 MB RAM, Jelly Bean 4.1.2, no Flash installed, Sync is set up A number of sites which used to work with FF17 now crash with FF18. Examples: http://www.williamsf1.com/home https://groups.google.com/group/mozilla.support.firefox/topics?lnk=srg FF just closes, no crash dump is created. Sometimes (not always) FF does not open properly after a crash. I.e. it opens a blank page with no content at all, no tabs, it just hangs and has to be closed. The next attempt to start it is then successful. Is anyone else seeing this? If so, are there open bugs? Another example where FF18 crashes, but I can't tell whether this worked with v17 before. http://www.dakar.com/index_DAKus.html Overall FF18 Mobile is a disappointment and a step backwards for me. Thanks.

Todas as respostas (4)

Donnie
Donnie
more options

Post your Crash Report ID's & I'll be able to check if there are any bugs related to this.

  1. Enter about:crashes in the Firefox location bar (that's where you enter your website names) and press Enter. You should now see a list of submitted crash reports.
  2. Copy the most recent 5 report IDs that you see in the crash report window and paste them into your forum response.

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

tibitts
tibitts Proprietário da pergunta
more options

BTDT. As already stated in the OP there are *no* crash reports.

Donnie
Donnie
more options

Really? You put no in quotes?

See:

https://bugzilla.mozilla.org/describecomponents.cgi?product=Firef...

tibitts
tibitts Proprietário da pergunta
more options

Really.

This bug would possibly be a match. https://bugzilla.mozilla.org/show_bug.cgi?id=731903

This may be related, but I'm really guessing here. https://bugzilla.mozilla.org/show_bug.cgi?id=744515

The behavior is similar as described here. https://bugzilla.mozilla.org/show_bug.cgi?id=747610

Should I open a new bug?