Avoid profiler initialization in exe context
Avoid profiler initialization in exe context

The profiler is "really" only useful in the
DLL, and there was one lingering Thread::SetName
call that (accidentally) initialized the
profiler in the exe context.  This change
avoids starting the profiler for that thread
which is only part of the exe, and is never used
for spawning or running tasks (profiled items).

r=rvargas
bug=103321
Review URL: https://chromiumcodereview.appspot.com/9432011

git-svn-id: de016e52bd170d2d4f2344f9bf92d50478b649e0@123047 0039d316-1c4b-4281-b951-d872f2087c98

ropik/chromium,adobe/chromium,yitian134/chromium,gavinp/chromium,gavinp/chromium,adobe/chromium,adobe/chromium,gavinp/chromium,gavinp/chromium,yitian134/chromium,yitian134/chromium,ropik/chromium,adobe/chromium,ropik/chromium,adobe/chromium,ropik/chromium,yitian134/chromium,gavinp/chromium,ropik/chromium,adobe/chromium,adobe/chromium,yitian134/chromium,gavinp/chromium,ropik/chromium,ropik/chromium,gavinp/chromium,adobe/chromium,yitian134/chromium,yitian134/chromium,gavinp/chromium,ropik/chromium,gavinp/chromium,ropik/chromium,yitian134/chromium,adobe/chromium,yitian134/chromium,yitian134/chromium,gavinp/chromium,adobe/chromium,adobe/chromium