Fix crbug/24815. Changes affect profiler "lazy" mode used for V8 in Chromium.
authormikhail.naganov@gmail.com <mikhail.naganov@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 28 Oct 2009 09:13:11 +0000 (09:13 +0000)
committermikhail.naganov@gmail.com <mikhail.naganov@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 28 Oct 2009 09:13:11 +0000 (09:13 +0000)
commit492dc0643fa3a48a0a2c30bb1668a371e9d35f0d
tree53b5c08e4cf6ede440eb92ab043558353b341ed3
parentabbc6b9147e1e56ec182420ff18da02371fb7177
Fix crbug/24815. Changes affect profiler "lazy" mode used for V8 in Chromium.

- don't engage the processing thread of CPU profiling until the first time profiling is resumed, this saves us a thread allocation for the majority of users;
- don't log shared libraries addresses: this is useless for JS-only profiling, and also consumes time on startup.

Review URL: http://codereview.chromium.org/340013

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3154 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/log.cc
test/cctest/test-log.cc