643314 - ess.chw.edu/lawson/portal crashes Minefield

Status: RESOLVED INVALID

(Core :: JavaScript Engine, defect)

Description

[Tiago Sá]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0

Just open it with Minefield 4b13pre or Firefox 4 RC2 and it crashes the browser. Spikes CPU usage and RAM usage and crashes.

Don't bother asking for new profiles and such, I wasn't born yesterday.

Reproducible: Always

Comment 1

[Mats Palmgren (inactive)]

Crash report ID for the crash you submitted? (in about:crashes)

Comment 2

[Matthias Versen [:Matti]]

I get a slow script warning and a second later a crash.
Socorro is unable to process my crash Reports from FF4.0RC1 and RC2 / win32

bp-3308803f-0008-476b-8976-dff622110320
bp-34c30225-ffc7-4458-a329-77ab42110320

Disabling both jit will change the result from a crash in a hang.

I will try to generate a stacktrace from windbg

Comment 3

[Matthias Versen [:Matti]]

Attachment: Windbg stacktrace

I'm not sure if this stack is right. A stack overflow with allocating memory ?

Comment 4

[Matthias Versen [:Matti]]

a bad guess from an amateur like me is JS Engine

Comment 5

[Alice0775 White]

The warning is
"Script: https://ess.chw.edu/lawson/portal/objects/PortalConfig.js:311"

An infinite loop happens.

for (var i = 0; i < len; i++)
{
  //do something
  for (var i = 0; i < nbrScripts; i++)
  {
   //do something
  }
}

Comment 6

[Alice0775 White]

Google Chrome 10.0.648.151 and  12.0.709.0 canary build also increases memory usage and crashes after for a while.

Comment 7

[Andreas Gal :gal]

Can you capture the page so we can reproduce this even if the site goes away?

Comment 8

[Alice0775 White]

Me?, I cannot.
I think this is the site issue(poor JS coding).

Comment 9

[Bob Clary [:bc] (inactive)]

A quick attempt to capture the page fails to reproduce. I'll see what I can do tomorrow.

Comment 10

[David Mandelin [:dmandelin]]

I was able to reproduce this, but my crash report doesn't seem to get processed. I tried in a debug build but it seems to be too slow to reach the crash.

I note that this site works only in IE9: it basically hangs in Fx, Chrome, and Safari. So, I'm not sure any action is required right now.

Comment 11

[Matthias Versen [:Matti]]

David: In my stack trace are several (200 ?) threads that look identical. Do you know why they this threads are spawned ?

Comment 12

[Josh Matthews [:jdm]]

In my experience, extra threads are either media related or background DNS resolution.  Not sure why there are so many doing nothing, however.

Comment 13

[Till Schneidereit [:till]]

Lawson Portal was changed to just shut out all browsers except for IE. :(