summaryrefslogtreecommitdiffstats
path: root/content/worker/worker_thread.cc
Commit message (Collapse)AuthorAgeFilesLines
* Allow linker initialization of lazy instancejoth@chromium.org2011-11-151-2/+2
| | | | | | | | | | | | | | Using the initializer list construct = {0} allows the object to be linker initialized. Modify the LazyInstance class design to make it a pod aggregate type that can be linker initialized this way. Also combines the instance and state members, in line with the Singleton<> class design. Introduces a new LAZY_INSTANCE_INITIALIZER macro specifically for using to init all lazy instances + modify all existing callsites to use it. (Old code would no longer compile) BUG=94925 TEST=existing tests pass. http://build.chromium.org/f/chromium/perf/linux-release/sizes/report.html?history=150&header=chrome-si&graph=chrome-si&rev=-1 should step downward. TBR=jam@chromium.org,rvargas@chromium.org,darin@chromium.org,ben@chromium.org,apatrick@chromium.org,akalin@chromium.org Review URL: http://codereview.chromium.org/8491043 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110076 0039d316-1c4b-4281-b951-d872f2087c98
* Removing dedicated worker-related IPC codei (first round). dslomov@chromium.org2011-10-271-10/+5
| | | | | | | | | | Since dedicated workers moved in-process, IPC-related code for them is unused. This is the first round of clean-up Review URL: http://codereview.chromium.org/8399007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107496 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_switches to content\public\common.jam@chromium.org2011-10-131-1/+1
| | | | | | | BUG=98716 Review URL: http://codereview.chromium.org/8277018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105389 0039d316-1c4b-4281-b951-d872f2087c98
* Update Chrome to use WebKitPlatformSupport instead of WebKitClient.abarth@chromium.org2011-09-021-3/+3
| | | | | | Review URL: http://codereview.chromium.org/7831035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99349 0039d316-1c4b-4281-b951-d872f2087c98
* If --disable-webgl is passed, continue to return null fromkbr@chromium.org2011-03-231-4/+0
| | | | | | | | | | | | | | | | | | Canvas.getContext("webgl"), but leave WebGLRenderingContext and related properties on the DOMWindow. Blacklisting of certain GPUs is resulting in reports that the browser doesn't support WebGL, when in reality only the graphics card doesn't. An upstream WebKit patch will follow this one removing the WebGL switch from WebRuntimeFeatures and removing the EnabledAtRuntime extended attribute from these properties. BUG=77110 TEST=none (verified manually) R=tony@chromium.org,darin@chromium.org,arv@chromium.org Review URL: http://codereview.chromium.org/6705015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@79160 0039d316-1c4b-4281-b951-d872f2087c98
* Move worker code from chrome\worker to content\worker.jam@chromium.org2011-03-141-0/+127
TBR=atwilson Review URL: http://codereview.chromium.org/6691004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78039 0039d316-1c4b-4281-b951-d872f2087c98