Closed Bug 493417 Opened 15 years ago Closed 12 years ago

Wolfram Alpha causing Firefox crashes/hangs?

Categories

(Core :: JavaScript Engine, defect)

1.9.2 Branch
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Dolske, Unassigned)

References

()

Details

(Keywords: top500)

Attachments

(2 files)

There seem to be reports of crashes/hangs on the newly-launched Wolfram Alpha site.

See comments in:

http://www.reddit.com/r/technology/comments/8kvey/wolframalpha_is_live/

A Twitter search for "Alpha firefox" also shows a number of recent tweets about crashes.

I couldn't find a good Digg thread, but didn't see anything in the Slashdot thread about the launch.

I've played around with the site since launch, and didn't notice anything -- although I did have one hang that may-or-may-not have been related (I had a lot of other tabs open). Blizzard just noted that he was seeing hangs.

Filing this for further investigation...
Flags: blocking-firefox3.6?
Flags: blocking-firefox3.5?
I can get my Shiretoko build to hang every time I go there (on mac.)
I just tried Wolfram Alpha using FF3.5b4, I received a scripting error which I regrettably did not copy... It didn't cause Firefox to crash, however, it did cause a slight hang and then brought up the scripting error.

After several retries I could not repeat this error.

I don't know if this Helps at all but I hope it brings some light on the matter.
Not sure why this should block Firefox 3.5's release; are we sure that we're the ones doing something wrong here?

Crash stacks or more debugging information would help.
Flags: blocking-firefox3.5? → blocking-firefox3.5-
A (relatively) high profile web site crashing the browser?  Sure - feels like it's something we should do.

Can we query the crash status info for crashes on the web site?  Looks like you can't do that from the public interface - was wondering if we could do it from inside?
In case this helps, I never got any *crashes* on the website, but I get frequent lockups, especially when the site is unresponsive.  This is with Firefox 3.0.10 on WinXP.
Same here - hangs, not crashes.  Otherwise I would have me some stack traces.
I tried banging away on Alpha in my debug trunk build, but wasn't able to reproduce a hang.
http://blog.wolframalpha.com/2009/05/20/still-hard-at-work/

"As we continue testing Wolfram|Alpha, we’ve noticed that users occasionally receive a 'Slow Script' warning when rendering Wolfram|Alpha pages. We hope to have a fix for this problem soon."
I also experience hangs with Firefox 3.0.10 on WinXP.
Adding topsite keyword, this site was covered at length in the Wall Street Journal as one of the popular pioneering search engines alongside Microsoft's Bling (soon to come) and others. Not sure if it qualifies it as a topsite, just wanted to throw this out there.
Keywords: top500
I got lucky and caught this in my current trunk build -- opt, with symbols, Dtrace enabled. The sample doesn't look too useful, but the DTrace funcflow output seems to indicate the page's JS is running wild, largely doing jQuery stuff. Alas, the filenames imply minimized JS, so the line numbers don't help much. :(

Odd that we're not getting a slow-script warning here...
FTR, the hang was on the results page for http://www21.wolframalpha.com/input/?i=Are+you+Skynet%3F after it had loaded and displayed the page.
--> Core::JavaScript based on comment 11
Assignee: nobody → general
Component: General → JavaScript Engine
Flags: blocking-firefox3.6?
Flags: blocking-firefox3.5-
Product: Firefox → Core
QA Contact: general → general
Version: Trunk → 1.9.2 Branch
Flags: blocking1.9.2?
FWIW, I haven't seen or heard of this recently. Though that could just be because Alpha's launch hype has died down.
-'ing for 1.9.2 for now.  Re-nom if someone sees this again and wants to argue.
Flags: blocking1.9.2? → blocking1.9.2-
I'm seeing this with Firefox 3.6.12 on CentOS 5.4 fully updated.  I can type "hello" into the wolfram alpha search box and submit and within 2 seconds or so Firefox completely crashes with a loud beep every time.  Using Minefield fully updated on Windows XP it works fine.  I'm going to do some experimentation on a fresh Firefox profile on the crashing browser etc. to see if I can narrow things down.  I have NoScript installed and so scripts were disabled on that site by default (in both Linux and XP test cases).
No activity in 2 years, this seems to have been fixed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: