Bug 22268
| Summary: | Profiler causes javascript failures. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Peter Mayo <petermayo> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ggaren, joepeck |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.5 | ||
Peter Mayo
When I load a test page that works fine without profiling I get a javascript exception.
Script debugging shows that one of the two arguments to a constructor is an unexpected value. Where I expect an instance of a class, the debugger reports a reference to the constructor function. The script bombs when the member properties are missing, unsurprisingly, from there.
This problem is new as of r38386 - same page, same test works fine on r38209 and r38297.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Peter Mayo
Also affects webkit-SVN-r38377.
Sorry, I can't share the specific web page at the moment - I'll try to reproduce with a public one the next time I have a gap to think about it.
Geoffrey Garen
Peter, do you have a way to reproduce this bug?
Peter Mayo
I don't have a public way to reproduce this just yet ... maybe real soon now.
Sorry,
Peter.
Joseph Pecoraro
I'm going to close this bug as invalid. Please open a new bug if you encounter JS issues while profiling.
Peter Mayo
Sounds Good. I have no memory of which piece was broken way back then.