Bug 79781
| Summary: | Web Inspector: weird performance when inspector is open | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | eustas.bug |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | loislo, pfeldman, vivekgalatage, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Linux | ||
eustas.bug
When I open Inspector, performance goes down more than 10x.
But when I start JavaScript CPU profiling, performance goes back to almost normal.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Vivek Galatage
Which port are we experiencing this performance issue? Gtk/Qt?
I tried this with QtTestBrowser built using the build-webkit for Qt port under ubuntu 11.10 and couln't see much difference in performance. Only a slight spike was observed in the system monitor for CPU during the inspector load and then eventually it came down to normal.
Same was observed while starting the Javascript CPU profiling.
Yury Semikhatsky
There was a problem in how V8 calculates //@ sourceUrl for large scripts(several megabytes). When capturing callstack e.g. for console messages we repeat this operation for each callframe which may be noticeably slow. We fixed that in V8 by caching search result: https://code.google.com/p/v8/source/detail?r=10902 this may need to be done for JSC as well.