Closed
Bug 884717
Opened 12 years ago
Closed 12 years ago
[Buri][Browser]Browse Google+ desktop version, it crashs
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 874678
People
(Reporter: sync-1, Unassigned)
Details
Attachments
(2 files)
AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.131
Firefox os v1.0.1
Mozilla build ID:20130606070202
Created an attachment (id=438141)
screenshot
DEFECT DESCRIPTION:
[Browser]Browse Google+ desktop version, it crashs.
REPRODUCING PROCEDURES:
1.Open www.google.com and log in with Google account(Google account: martellxin.com, password:martellxin)
2.Click the user's name which is at the top right corner, then it enters to Google+ page.
3.Move to the bottom of the page and click " Desktop version"
4.During the loading the page, it crashs like screenshot.
5.Click reload, crashs again.
EXPECTED BEHAVIOUR:
The page can opens normally, no crash.
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
TOOLS AND PLATFORMS USED:
USER IMPACT:
REPRODUCING RATE:4/5
For FT PR, Please list reference mobile's behavior:
Updated•12 years ago
|
Comment 5•12 years ago
|
||
What is probably happening here is that the desktop site is using up all available memory so the operating system is killing the content process in which that web site is running to prevent the whole OS from crashing. It then informs the browser app that it has killed the process and the browser app shows the message displayed in the screenshot. This is intended behaviour.
If there is a mobile optimised version of this web site then Google should be serving a version more appropriate to the device.
Severity: critical → normal
Component: Gaia::Browser → Mobile
Keywords: crash
Priority: P1 → --
Product: Boot2Gecko → Tech Evangelism
Whiteboard: [b2g-crash]
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•6 years ago
|
Product: Tech Evangelism → Web Compatibility
| Assignee | ||
Updated•1 year ago
|
Component: Mobile → Site Reports
You need to log in
before you can comment on or make changes to this bug.
Description
•