Bug 26728 – Web Inspector: [JSC] crashes in JSC::InternalFunction::calculatedDisplayName

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector (Deprecated)

[Patrick Mueller]

I've been seeing this on and off since the displayName support was added.  As I was instrumenting the Dojo library to liberally apply displayName programmatically, I started seeing them more often.  Figured it was time to report it.  I'll attach a stack trace; I always see the calculatedDisplayName method at the top of the stack, but believe I've seen not just + 17 (assume that's an offset from top of function), but a +38 as well. I'll start attaching more if I see different shaped stack traces.

[Patrick Mueller]

Created attachment 31872 [details]
stack trace from debugging with instrumented Dojo doing a number of displayName settings

Stack trace from a debugging session (no profiling) where I had instrumented Dojo to perform programmatic displayName assignments for it's class declaration capabilities.

[Mark Rowe (bdash)]

<rdar://problem/7008019>

[Patrick Mueller]

I suspect a reduction will take some time.  I can provide a recipe that includes downloading dojo, dojo samples, adding a few lines of code to a dojo file, and then running a sample, setting some breakpoints, running the sample, etc.  But I suspect you'd like something smaller/easier; or would that be good enough?

One other note that may be relevant; when debugging I typically run the debugger undocked; as I'm debugging my code, I change that code in a text editor, and reload the web page, leaving the debugger up.  Would also typically have breakpoints set in the code.  Perhaps there are stale references to displayName strings in the debugger?

[Blaze Burg]

I believe this was fixed. Re-open if you hit it again.