Ignore:
Timestamp:
Oct 7, 2015, 4:10:20 PM (10 years ago)
Author:
[email protected]
Message:

Unreviewed, rolling back in r190450
https://bugs.webkit.org/show_bug.cgi?id=149727

This time for sure?

The cause of the leak was an invalidated compilation.

There was vestigial manual memory management code that eagerly removed
a CodeBlock from the set of CodeBlocks if compilation was invalidated.
That's not cool since we rely on the set of CodeBlocks when we run
destructors.

The fix is to remove the vestigial code.

I ran the leaks, correctness, and performance tests locally and did not
see any problems.

Restored changesets:

"CodeBlock should be a GC object"
https://bugs.webkit.org/show_bug.cgi?id=149727
http://trac.webkit.org/changeset/190450

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/heap/Heap.h

    r190679 r190694  
    225225        template<typename T> void releaseSoon(RetainPtr<T>&&);
    226226#endif
    227 
    228     void removeCodeBlock(CodeBlock* cb) { m_codeBlocks.remove(cb); }
    229227
    230228    static bool isZombified(JSCell* cell) { return *(void**)cell == zombifiedBits; }
     
    313311    void deleteSourceProviderCaches();
    314312    void notifyIncrementalSweeper();
    315     void rememberCurrentlyExecutingCodeBlocks();
     313    void writeBarrierCurrentlyExecutingCodeBlocks();
    316314    void resetAllocators();
    317315    void copyBackingStores();
Note: See TracChangeset for help on using the changeset viewer.