JIT causes Maemo Tp3 sexuploader.com crash

RESOLVED FIXED

Status

()

Core
JavaScript Engine
--
critical
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: aki, Unassigned)

Tracking

Trunk
ARM
Maemo
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

53.96 KB, application/octet-stream
Details
(Reporter)

Description

9 years ago
Created attachment 389516 [details]
crasher page tarball

This doesn't seem to be an issue if you go to either sexuploader.com or megarotic.com on the internet.  However, the cached Tp3 page for www.sexuploader.com/www.megarotic.com/index.html crashes Tp3 reliably with JIT turned on.

I'm able to crash manually going to that page via http://localhost or file:///.

Attaching the www.sexuploader.com Tp3 directory since the Tp3 pageset isn't in general circulation... the page in question is www.sexuploader.com/www.megarotic.com/index.html

Marking confidential due to Talos Tp pageset policies.
Tp is legally fine to distribute, we're just a bit stuck on the content before we distribute en masse.  Opening, because we're going to want some general eyes on this.

Do you get a stack?
Group: mozilla-corporation-confidential
(Reporter)

Comment 2

9 years ago
Not right now, just a segfault.

I'd like to eventually get the standard Talos stack trace going on Maemo, but we don't currently build symbols and Ted says the minidump is blocked for Maemo currently.  Also, I've been told that automated stack dumps isn't a high priority compared to the other mobile work.
(Reporter)

Comment 3

9 years ago
Not sure what fixed this, but in the course of enabling tracemonkey I enabled both jit and non-jit runs of talos.  When I saw the jit runs going green, I made those default.  This is fixed.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.