Add trace code to track all posted tasks in message_loop and WorkerThreads (non-official builds only).

It's very helpful to understand what chrome is doing at runtime. Sometimes a thread in chrome does something expensive that causes a frame hitch. With this change, any expensive task will show up clearly in traces, with the file/function of where the task was posted.

TEST=go to about:tracing, run a trace and notice that all tasks are traced.

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103740 0039d316-1c4b-4281-b951-d872f2087c98


CrOS-Libchrome-Original-Commit: 19d8a90fbc1fd7c26a873dc84fcbc875c509cf11
9 files changed
tree: 789d28e9c87a886180e665c64e1372be539d1b99
  1. base/
  2. build/
  3. dbus/
  4. ipc/
  5. testing/
  6. third_party/