869967 - SIGSEGV, maybe involves Javascript

Status: RESOLVED DUPLICATE of bug 867935

(Firefox :: Untriaged, defect)

Description

[M ODonnell]

User Agent: Mozilla/5.0 (X11; Linux i686; rv:23.0) Gecko/20130508 Firefox/23.0
Build ID: 20130508031113

Steps to reproduce:

Allowed Nightly to update itself, then visited this page:

  http://www.harvardvanguard.org/become-a-patient/pcps-with-open-panels#chelmsford

...and followed link on that page to the page for Dr. Wooseung Lee:

  http://www.harvardvanguard.org/clinicians/wooseung-lee-4672


Actual results:

Shortly after loading that second page, and possibly involving some movement of the mouse pointer without any clicks, the browser died with a SIGSEGV.  This seems to be quite repeatable, even if I completely delete my entire ~/.mozilla hierarchy, ie. even if I run a completely "virgin" (unmodified, no add-ons, etc) Firefox


Expected results:

Should not have crashed.

Comment 1

[M ODonnell]

FWIW, when I run this in my normal (non-"virgin") mode with my usual collection of add-ons and extensions active, and if I use NoScript to prevent Javascript from executing on that site, no SIGSEGV is seen.

Comment 2

[Scoobidiver (away)]

Please provide a stack trace (see https://developer.mozilla.org/docs/How_to_get_a_stacktrace_for_a_bug_report).

Comment 3

[M ODonnell]

Signature of crash on my machine appears to be

  bp-f7034759-d2be-4b47-a376-c30282130508 05/08/2013      01:59 PM

Comment 4

[M ODonnell]

Attachment: A dump from one of the crashes in question.

A dump from one of the crashes in question is attached.  Sorry if that's redundant - are they also being transmitted automatically?

Comment 5

[M ODonnell]

Attachment: The "extra" file associated with that attached dump image.

The "extra" file associated with that attached dump image.

Comment 6

[Scoobidiver (away)]

It's basically bug 867935 for NVIDIA 304.64.