Bug #7961

Crash in parser/renderer, hopefully without memory corruption? Orfox-1.2release

Added by Anonymous over 1 year ago.

Status:NewStart date:10/01/2016
Priority:HighDue date:
Assignee:-% Done:


Category:-Estimated time:2.00 hours
Target version:-


Steps to reproduce;
open https://play.google.com/store/apps/details?id=de.j4velin.wifiAutoOff with latest Orfox from F-Droid
Scroll up and down a dozen or so times. It will scroll very slowly like there was a ton of scripts running or something (it didn't do this in ESR38.1 without a ton of tabs open).

Opening over 50 or tabs in the old version made it instable to the point where it would sometimes crash just while scrolling a page, but there were only a few tabs open, so it might have been memory exhaustion in the old ESR38.1, but it would be nice to know if there is remote code execution in the ESR45 just from normal browsing.
There was little to no CPU/net usage by anything else (in 38.1 and 45.4).

Plugins/media(except images); never load(because of stagefright 2.0)
javascript.enabled=false(since NoScript exempts all popular sites by default)
All autoupdate stuff in about:config disabled(since no word if pinning was fixed in fennec)
Everything else stock

Sorry, no.

Keep up the great work, this is all that's between humanity and total oppression.
Just confirming that this is merely DoS and not ltherwise exploitable would be a huge relief.
The 2 hour estimate is just to confirm that it's safe to browse with no javascript/plugins, not to fix the crash.

Related issues

Copied to Orfox Private Browser - Bug #8032: Crash in parser/renderer, hopefully without memory corrup... New 10/01/2016

Also available in: Atom PDF