We've got complains that sending afterCompile events to debug message handler may...
authoryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 3 Jul 2009 10:02:51 +0000 (10:02 +0000)
committeryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 3 Jul 2009 10:02:51 +0000 (10:02 +0000)
commit48a99323a4f1c5f2053c287a6324af3bb6044171
tree3f4e953c91565d1bda0bc2984663b92fda7a7792
parentd53e5f8d8a467ea7815e9347372b27fda7c43523
We've got complains that sending afterCompile events to debug message handler may have considerable impact on the profiler when inspected script does lots of 'eval's. The proposed solution is to request source of the compiled script lazily instead of sending it in afterCompile event.

Corresponding Chromium bug:
http://code.google.com/p/chromium/issues/detail?id=15913
Review URL: http://codereview.chromium.org/149176

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2349 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/debug-delay.js