- 06 Apr, 2011 1 commit
-
-
vitalyr@chromium.org authored
We can only call malloc/free once per group and we can avoid scanning through a list of NULLs if we keep unprocessed groups in the beginning. I also changed the internal representation of implicit references to hold a handle to the parent (instead of a direct pointer). The prologue callback must not trigger a GC, but it's better to be safe. Review URL: http://codereview.chromium.org/6800003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7521 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 18 Mar, 2011 3 commits
-
-
vitalyr@chromium.org authored
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7271 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
vitalyr@chromium.org authored
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7269 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
vitalyr@chromium.org authored
Review URL: http://codereview.chromium.org/6685088 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7268 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 16 Mar, 2011 1 commit
-
-
antonm@chromium.org authored
Those are necessary to properly manage relationship between objects in cases when they don't form proper tree structure. Review URL: http://codereview.chromium.org/6686053 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7202 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 10 Mar, 2011 1 commit
-
-
mikhail.naganov@gmail.com authored
objects retained by object groups and global handles. This information is then used during heap snapshot generation to provide a more complete memory picture. This patch will be needed to fix https://bugs.webkit.org/show_bug.cgi?id=53659. Review URL: http://codereview.chromium.org/6626043 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7125 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 02 Mar, 2011 1 commit
-
-
mmaly@chromium.org authored
Review URL: http://codereview.chromium.org/6594037/ Revert "Revert "Assignment to read only properties throws in strict mode."" This reverts commit aefcd82e1d36d458dd071ebf4777340f08aa67b1. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7007 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 01 Mar, 2011 2 commits
-
-
mmaly@chromium.org authored
This reverts commit 503f2a501e504f330821f247074e731aa649b1f0. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6977 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mmaly@chromium.org authored
Review URL: http://codereview.chromium.org/6594037/ git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6976 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 07 Dec, 2010 3 commits
-
-
kasperl@chromium.org authored
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5922 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kasperl@chromium.org authored
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5921 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kasperl@chromium.org authored
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5920 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 10 Nov, 2010 2 commits
-
-
ager@chromium.org authored
Review URL: http://codereview.chromium.org/4764002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5800 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ager@chromium.org authored
Add 128MB limit for executable pages. BUG=http://code.google.com/p/v8/issues/detail?id=925 TEST=None. TBR=jschuh@chromium.org Review URL: http://codereview.chromium.org/4634003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5799 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 25 Oct, 2010 1 commit
-
-
erik.corry@gmail.com authored
Review URL: http://codereview.chromium.org/3970005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5698 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 18 Oct, 2010 1 commit
-
-
antonm@chromium.org authored
This was only used by Heap::CollectGarbage to check if after GC available space is bigger than was requested, but nobody checked the value returned by Heap::CollectGarbage, so requested size was efficiently unused. However, it may trigger spurious out of memory exceptions if requested size is big enough. BUG=http://code.google.com/p/chromium/issues/detail?id=54580 Review URL: http://codereview.chromium.org/3836001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5642 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 19 Jul, 2010 1 commit
-
-
antonm@chromium.org authored
If object enters NEAR_DEATH state, it must be explicitly cleared and/or disposed, otherwise it would retain JS object forever. Note as well that parameter is reset to NULL on first invocation so weak handle callback would be in hard situation. Review URL: http://codereview.chromium.org/3011009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5096 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 19 Jan, 2010 1 commit
-
-
antonm@chromium.org authored
Review URL: http://codereview.chromium.org/543113 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3655 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 21 Oct, 2009 1 commit
-
-
ager@chromium.org authored
when using snapshots. The alignment of new space has to match the alignment in the snapshot, but the max committed amount of memory does not. For now, we assume that the default semispace size is always used in a snapshot. Review URL: http://codereview.chromium.org/300036 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3106 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 17 Jul, 2009 1 commit
-
-
whesse@chromium.org authored
Many X64 bugs have been due to the difference between (unaligned) Array::kHeaderSize and (aligned) FixedArray::kHeaderSize. Review URL: http://codereview.chromium.org/155687 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2502 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 18 Jun, 2009 1 commit
-
-
bak@chromium.org authored
This avoids back-to-back mark-sweep collections. Review URL: http://codereview.chromium.org/136001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2219 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 11 Dec, 2008 1 commit
-
-
deanm@chromium.org authored
The main goal was to improve O(n^2) behavior when there are many object groups. The old API required the grouping to be done on the v8 side, along with a linear search. The new interface requires the caller to do the grouping, passing V8 entire groups at a time. This removes the group id concept on the v8 side. - Changed AddObjectToGroup to AddObjectGroup. - Removed the group id concept from the V8 side. - Remove a static constructor while I'm here, lazily initialize the object groups list. - Cleaned up return by non-const references to return pointers. Review URL: http://codereview.chromium.org/13341 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@965 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 23 Oct, 2008 1 commit
-
-
christian.plesner.hansen@gmail.com authored
- Changed WeakReferenceCallback to take a Persistent<Value> instead of a Persistent<Object>. - Removed Message::GetUnderline and Message::GetScriptData. - Added Value::IsDate, Date::Cast and Date::Value. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@564 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 12 Sep, 2008 1 commit
-
-
deanm@chromium.org authored
This is a new static flag system, designed to have all flags in a central place, and compiled into the binary without requiring static constructors for registration. All flags are moved out of the specific modules and into flags.defs, with different sections for debug, release, etc. The flag variables are always defined. For example, a debug flag in release mode still exists, but is read only and set to the default value. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@296 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Sep, 2008 1 commit
-
-
christian.plesner.hansen@gmail.com authored
Added presubmit step to check copyright. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@242 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 08 Sep, 2008 1 commit
-
-
kasperl@chromium.org authored
snapshot. Changed the debug-script.js test to ignore the exact number of extension scripts. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@199 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 05 Sep, 2008 1 commit
-
-
erik.corry@gmail.com authored
* Make old_data_space non-executable on OSs and hardware that support it. * Rename old_space to old_pointer_space (can contain pointers, esp. to new space). * Ensure that individual pages allocated for old_space are only executable when they are for code objects. * Ensure Space::Setup can cope with non-aligned memory. * Make some methods on Spaces virtual. Make a way to iterate over all spaces. * Replace executability flag with Executability enum in order to make intent at call site clearer. * Fix serialization/deserialization to allocate write barrier memory for large arrays. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@165 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 22 Aug, 2008 1 commit
-
-
christian.plesner.hansen authored
In the shell sample don't print the result of executing a script, only evaluating expressions. Fixed issue when building samples on Windows using a shared V8 library. Added visibility option on Linux build which makes the generated library 18% smaller. Changed build system to accept multiple build modes in one build and generate seperate objects, libraries and executables for each mode. Removed deferred negation optimization (a * -b => -(a * b)) since this visibly changes operand conversion order. Improved parsing performance by introducing stack guard in preparsing. Without a stack guard preparsing always bails out with stack overflow. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-