Ignore:
Timestamp:
Jan 8, 2010, 5:02:38 PM (15 years ago)
Author:
[email protected]
Message:

2010-01-08 Geoffrey Garen <[email protected]>

Reviewed by Oliver Hunt.

Memory use grows grows possibly unbounded in this JavaScript Array test case
https://bugs.webkit.org/show_bug.cgi?id=31675

This fixes one observed bug in this test case, which is that
arrays don't report extra cost for the sparse value maps.

SunSpider reports a small speedup.

  • runtime/JSArray.cpp: (JSC::JSArray::putSlowCase): Report extra memory cost for the sparse value map.
  • runtime/JSArray.h:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/JavaScriptCore/runtime/JSArray.h

    r49721 r53025  
    3333        SparseArrayValueMap* m_sparseValueMap;
    3434        void* lazyCreationData; // A JSArray subclass can use this to fill the vector lazily.
     35        size_t reportedMapCapacity;
    3536        JSValue m_vector[1];
    3637    };
Note: See TracChangeset for help on using the changeset viewer.