Created attachment 60639 [details] file to help reproduce this bug Users should be a able to start/stop profiling while the javascript code is running. For example, in an attached page, once javascript enters infinite loop, if the user tries to start CPU profiling or take heap snapshot - nothing will happen. Also if the CPU profiler is already running the user will not be able to stop it. Desired behavior: CPU profiler / Heap snapshotting should be independent of the javascript, since it is especially useful in such cases where the code is already running.
Sorry for having you misguided, but this bug doesn't actually depend on async breakpoints.
Created attachment 61388 [details] assuming that http://codereview.chromium.org/2962007 has landed, here is the patch
Attachment 61388 [details] did not build on chromium: Build output: http://webkit-commit-queue.appspot.com/results/3453263
Was fixed in a more general way in bug 43900.