Fix rare access violation during JS heap serialization.

src/serialize.cc

Index: src/serialize.cc
===================================================================
--- src/serialize.cc	(revision 23468)
+++ src/serialize.cc	(working copy)
@@ -1539,7 +1539,8 @@
           current_contents == current[-1]) {
         DCHECK(!serializer_->isolate()->heap()->InNewSpace(current_contents));
         int repeat_count = 1;
-        while (current < end - 1 && current[repeat_count] == current_contents) {
+        while (&current[repeat_count] < end - 1 &&
+            current[repeat_count] == current_contents) {
           repeat_count++;
         }

[Slava Chigrin, 2014/08/27 17:06:01]

Before that sometimes current[repeat_count] can go beyound |end| pointer and
cause access violation if current object placed at the end of page.

         current += repeat_count;