The serializer skips to next page if current obj size exceeds the current page (see SimulatedHeapSpace::Allocate()). I could be wrong: under certain circumstances, it depends on the order of visiting objects: the simulated heap created during serialization might be bigger than the original heap. But serializer is writing the size of original heap space into header.
deserializer is using the original heap page size in header to create the page_list. The length of page_list could be smaller than the original heap space. Later it causes following assertion fail in ResolvePaged(): ASSERT(page_index < page_list->length()); --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
