Bug 21165
| Summary: | console.profile() crashing the browser | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | boucher <rboucher> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | Normal | CC: | joepeck |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac (Intel) | ||
| OS: | OS X 10.5 | ||
boucher
One call to console.profile() followed by console.profileEnd() seems to work fine. When I started a second profile, I accidentally had it followed with console.endProfile(), which was causing a crash. I can't reproduce with a simple test case, but here's the crash report. Hope its helpful.
http://paste.lisp.org/display/67514
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mark Rowe (bdash)
<rdar://problem/6252646>
Joseph Pecoraro
The crash log is now gone so there isn't anything actionable here. However, the new sampling profiler completely changes the vast majority of code that runs when console.profile/profileEnd are used. Very little, if anything, remains of what did in 2008 =). Closing.