搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Each request to a website crashes with the message "Something went wrong while displaying a web page".

  • 6 回覆
  • 39 有這個問題
  • 6 次檢視
  • 最近回覆由 Serratus

more options

I'm using a HTC Desire S with Android 2.3.3 and installed the latest version of Firefox Mobile (4.0b13pre). Not even a single page loads, just the homescreen works fine.

I'm using a HTC Desire S with Android 2.3.3 and installed the latest version of Firefox Mobile (4.0b13pre). Not even a single page loads, just the homescreen works fine.

所有回覆 (6)

more options

Sorry about the crashes, and thanks for the report.

If you type "about:crashes" in the location bar and press enter/go, are there any crash reports listed?

Is this an unofficial version of Android 2.3.3? If so, you might want to try Firefox on an official Android release, or see if there are any updates available for your unofficial version.

more options

Thanks for the quick reply.

Yes, there are all my reports listed, but I can't open any one of them, because the same crash message rises.

I'm running the official version of Android 2.3.3. It's the new HTC Desire S which gets shipped with this ROM.

more options

Thanks again for the information. Can you copy one of the crash links from about:crashes? You can press-and-hold on the link, and then choose "Share Link" to send it to yourself via email or other method, then paste it here. (Or you can send it directly to me at mbrubeck@mozilla.com.)

more options

Here is the last produced crash which was reported: http://crash-stats.mozilla.com/report/index/bp-9cb7ca4d-e5b3-4db6-a3f8-578a72110329

Hope this is a lead to solving this problem. Another question: Is my previously mentioned version of Firefox mobile the latest available? I just read somewhere, that the final version was released today, but I can't find any build with a "final" buildstring.

more options

Thanks for the information. This is a bug that we saw previously in some unofficial ROMs like Cyanogenmod, though it was quickly fixed in those ROMs. It looks like some device manufacturers might have ended up shipping the same buggy code. We're tracking this issue at:

https://bugzilla.mozilla.org/show_bug.cgi?id=626051

more options

Thanks for the dispatching my problem to the Bugtracker. I'll follow the conversation and wait for a proper fix.