Removed HeapTimer::synchronize
authorggaren@apple.com <ggaren@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 18 Apr 2013 21:55:22 +0000 (21:55 +0000)
committerggaren@apple.com <ggaren@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 18 Apr 2013 21:55:22 +0000 (21:55 +0000)
commit3191eae64bf12c073e7c40241739b6a1c963f06f
tree35d5fc998a2f2acefb6e8596b307790672a317b9
parente0597af65704dba9c7485d461348f1b6715c863f
Removed HeapTimer::synchronize
https://bugs.webkit.org/show_bug.cgi?id=114832

Reviewed by Mark Hahnenberg.

HeapTimer::synchronize was a flawed attempt to make HeapTimer thread-safe.
Instead, we use proper locking now.

This is a slight API change, since the GC timer will now only fire in the
run loop that created the JS VM, even if another run loop later executes
some JS.

* API/APIShims.h:
(JSC::APIEntryShimWithoutLock::APIEntryShimWithoutLock):
* heap/HeapTimer.cpp:
(JSC):
* heap/HeapTimer.h:
(HeapTimer):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@148704 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/JavaScriptCore/API/APIShims.h
Source/JavaScriptCore/ChangeLog
Source/JavaScriptCore/heap/HeapTimer.cpp
Source/JavaScriptCore/heap/HeapTimer.h