Updates:
Summary: mjsunit/regress/regress-crbug-501711 fails flakily with concurrent isolates.

Comment #1 on issue 4378 by [email protected]: mjsunit/regress/regress-crbug-501711 fails flakily with concurrent isolates.
https://code.google.com/p/v8/issues/detail?id=4378

Repro:

GYP_GENERATORS=ninja GYP_DEFINES="target_arch=ia32 v8_enable_slow_dchecks=1 v8_optimized_debug=1 v8_target_arch=ia32 use_goma=1" gclient sync
ninja -C out/Debug d8 -j1000
ulimit -c unlimited
tools/run-tests.py --random-seed-stress-count=100 --isolates mjsunit/regress/regress-crbug-501711 --mode=Debug --arch=ia32 --buildbot
gdb out/Debug/d8 core

[...]

[New LWP 25093]
[New LWP 25018]
[New LWP 24983]
[New LWP 25020]
[New LWP 25021]
[New LWP 25016]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/grte/v4/lib64/libthread_db.so.1".
Core was generated by `/usr/local/google/home/yangguo/v8/out/Debug/d8 --test --random-seed=45086933 --'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x084c2220 in CopyCharsUnsigned<unsigned char, unsigned short> (dest=<optimized out>, src=<optimized out>, chars=<optimized out>)
    at ../../src/utils.h:1413
1413        while (dest < limit) *dest++ = static_cast<sinkchar>(*src++);
Unable to determine compiler version.
Defaulting to None libstdc++ pretty-printers.
(gdb) info threads
  Id   Target Id         Frame
  6    Thread 0xf73a7b40 (LWP 25016) 0xf76f5440 in __kernel_vsyscall ()
  5    Thread 0xf5ba4b40 (LWP 25021) 0xf76f5440 in __kernel_vsyscall ()
  4    Thread 0xf63a5b40 (LWP 25020) 0xf76f5440 in __kernel_vsyscall ()
3 Thread 0xf73a9700 (LWP 24983) 0xf770deae in ?? () from /lib/ld-linux.so.2
  2    Thread 0xf6ba6b40 (LWP 25018) 0xf76f5440 in __kernel_vsyscall ()
* 1 Thread 0xf51ffb40 (LWP 25093) 0x084c2220 in CopyCharsUnsigned<unsigned char, unsigned short> (dest=<optimized out>, src=<optimized out>,
    chars=<optimized out>) at ../../src/utils.h:1413
(gdb) t 3
[Switching to thread 3 (Thread 0xf73a9700 (LWP 24983))]
#0  0xf770deae in ?? () from /lib/ld-linux.so.2
(gdb) bt
#0  0xf770deae in ?? () from /lib/ld-linux.so.2
#1  0xf7705c5d in ?? () from /lib/ld-linux.so.2
#2  0xf76fefa4 in ?? () from /lib/ld-linux.so.2
#3  0xf76ff7aa in ?? () from /lib/ld-linux.so.2
#4  0xf7704181 in ?? () from /lib/ld-linux.so.2
#5  0xf770a500 in ?? () from /lib/ld-linux.so.2
#6  0xf761ef63 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#7  0xf770535c in ?? () from /lib/ld-linux.so.2
#8  0xf73de1b1 in ?? () from /lib/i386-linux-gnu/libc.so.6
#9  0xf73de20d in exit () from /lib/i386-linux-gnu/libc.so.6
#10 0x08052d4e in v8::Shell::QuitOnce (args=<optimized out>) at ../../src/d8.cc:817 #11 0x08a7413f in v8::base::CallOnceImpl (once=0x96acb28 <v8::Shell::quit_once_>, init_func=0xf761322a, arg=0xf76c056c) at ../../src/base/once.cc:37 #12 0x08053359 in CallOnce<v8::FunctionCallbackInfo<v8::Value> > (arg=0xf76c056c, once=<optimized out>, init_func=<optimized out>) at ../../src/base/once.h:95
#13 v8::Shell::Quit (args=...) at ../../src/d8.cc:822
#14 0x087d1292 in v8::internal::FunctionCallbackArguments::Call (this=0xffe58f50, f=0x8053330 <v8::Shell::Quit(v8::FunctionCallbackInfo<v8::Value> const&)>)
    at ../../src/arguments.cc:33
#15 0x0813b3b2 in v8::internal::HandleApiCallHelper<false> (isolate=0x9bd0cf0, args=...) at ../../src/builtins.cc:1010 #16 0x08141793 in Builtin_Impl_HandleApiCall (args=..., isolate=<optimized out>) at ../../src/builtins.cc:1033 #17 v8::internal::Builtin_HandleApiCall (args_length=<optimized out>, args_object=<optimized out>, isolate=0x9bd0cf0) at ../../src/builtins.cc:1029
#18 0xf520bb9c in ?? ()
#19 0xf523200e in ?? ()
#20 0xf5232095 in ?? ()
#21 0xf5232095 in ?? ()
#22 0xf5232095 in ?? ()
#23 0xf5232095 in ?? ()
#24 0xf5232095 in ?? ()
#25 0xf5232095 in ?? ()
#26 0xf5232095 in ?? ()
#27 0xf5232095 in ?? ()
#28 0xf5232095 in ?? ()
#29 0xf5232095 in ?? ()
#30 0xf5232095 in ?? ()
#31 0xf5232095 in ?? ()

[...]


Note that by specifying --isolates for run-tests.py, we run the same test on two isolates, each on its own thread. Apparently this causes QuitOnce to fail flakily for some reason.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to