Closed
Bug 1242134
Opened 9 years ago
Closed 8 years ago
crashing without report screen
Categories
(Firefox for Android Graveyard :: Toolbar, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: nschubach, Unassigned)
Details
User Agent: Mozilla/5.0 (Android 5.1.1; Tablet; rv:46.0) Gecko/46.0 Firefox/46.0
Build ID: 20160122030244
Steps to reproduce:
General browsing (reddit, newegg, amazon)
Actual results:
Nightly build now crashes hard with no crash reporting option.
Expected results:
Crash submit screen should show if it crashes. Also should not crash so much (seems to happen @10-15 min)
Reporter | ||
Updated•9 years ago
|
OS: Unspecified → Android
Hardware: Unspecified → ARM
Version: Trunk → 46 Branch
Reporter | ||
Comment 1•9 years ago
|
||
I think I can reproduce it regularly:
Go to: http://120hzmonitors.com/144hz-monitor-buyers-guide-january-2016/
Click on High End Link on the right
Open the Asus and Acer monitor links to Amazon in new tabs (The names above the pictures are links)
Select the Asus tab
Scroll down to reviews, wait for page to load
Open all reviews
Scroll down to first and open comments
This just about crashes me every time.
Comment 2•9 years ago
|
||
This is likely the layers issues we are investigating.
Component: General → Graphics, Panning and Zooming
Comment 3•9 years ago
|
||
When it crashes without a crash reporting option it's usually because of an out-of-memory condition.
Comment 4•8 years ago
|
||
There have been a number of fixes made to reduce memory usage, are you still able to reproduce this? If so, would you be able to get a logcat from your device when this happens?
Flags: needinfo?(nschubach)
Reporter | ||
Comment 5•8 years ago
|
||
I have not seen this bug in a long time. I believe it was fixed a few months ago.
Comment 6•8 years ago
|
||
Thanks for verifying!
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(nschubach)
Resolution: --- → WORKSFORME
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•