Last Comment Bug 812217 - Crash on Lucidchart benchmark
: Crash on Lucidchart benchmark
Status: RESOLVED WONTFIX
: crash, stackwanted
Product: Core
Classification: Components
Component: Graphics (show other bugs)
: 16 Branch
: x86 Windows 8
: -- critical (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
: Milan Sreckovic [:milan]
Mentors:
http://www.lucidchart.com/blog/2012/1...
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-15 09:50 PST by Nick Cameron [:nrc]
Modified: 2012-12-04 13:15 PST (History)
5 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Nick Cameron [:nrc] 2012-11-15 09:50:00 PST
Apparently we crash a benchmark from Lucidchart, I couldn't see a link to download the benchmark so I don't know any more details. From the hacker news discussion (http://news.ycombinator.com/item?id=4788601): "Interestingly, the part that crashed Firefox was one of the simpler tests--typing a bunch of text content in, then resizing and rotating the shapes that contain that text. Firefox didn't give any details as to why it crashed.

The only thing I could even measure that would lead to a crash is memory usage. I just re-ran the test and watched the process's memory usage. It hovered in the 300-400MB range during the first third of the test. Then, during the test I describe, memory usage rocketed to around 1GB, at which point the browser crashed hard."

So maybe another canvas/memory usage bug? Possibly we've fixed this already, 16 is getting kinda old. I will email them to get more details.
Comment 1 Nick Cameron [:nrc] 2012-11-15 09:53:26 PST
Couldn't find an email address, so left a comment on the article to get in touch.
Comment 2 Nick Cameron [:nrc] 2012-12-04 13:15:14 PST
I haven't had any contact from the guys behind the benchmark (beyond a single comment on their page, which I replied to but got not reply top in turn). I can't analyse this without code, or at least some more details, and it doesn't look like we're going to get that, so I'm going to close this, if anyone objects, or has suggestions for how to approach this (or even better, you're associated with the benchmark and want to give us something to work with), please reopen (or email me to do so). Thanks.

Note You need to log in before you can comment on or make changes to this bug.