Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault on Dart VM as HTTP server #15952

Closed
DartBot opened this issue Jan 7, 2014 · 2 comments
Closed

Segfault on Dart VM as HTTP server #15952

DartBot opened this issue Jan 7, 2014 · 2 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@DartBot
Copy link

DartBot commented Jan 7, 2014

This issue was originally filed by sestegr...@gmail.com


After about 20 minutes of requests on a HTTP server implemented with Dart VM, a segfault occurs.
Dart VM version 1.0.0.10_r30798 on Linux 64 bits

$ dmesg
dart[6022]: segfault at 7fe55cf51058 ip 00007fe5593a94e3 sp 00007fe558e1e7d0 error 7

$ gdb dart core.32564
Program terminated with signal 11, Segmentation fault.

­0 0x00007fe5593a94e3 in ?? ()

(gdb) thread apply all bt

Thread 5 (Thread 0x7fe55a164700 (LWP 32570)):

­0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162

­1 0x0000000000461912 in dart::Monitor::Wait (this=0xfbe4d0, millis=0) at runtime/platform/thread_linux.cc:262

­2 0x0000000000467a78 in dart::bin::ExitCodeHandler::ExitCodeHandlerEntry (param=<value optimized out>)

    at runtime/bin/process_linux.cc:174

­3 0x0000000000462671 in dart::ThreadStart (data_ptr=<value optimized out>) at runtime/platform/thread_linux.cc:85

­4 0x00000034d1407851 in start_thread (arg=0x7fe55a164700) at pthread_create.c:301

­5 0x00000034d0ce894d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 4 (Thread 0x7fe55cf10700 (LWP 32566)):

­0 0x00000034d0ce8f43 in epoll_wait () at ../sysdeps/unix/syscall-template.S:82

­1 0x0000000000463912 in dart::bin::EventHandlerImplementation::Poll (args=16685120) at runtime/bin/eventhandler_linux.cc:406

­2 0x0000000000462671 in dart::ThreadStart (data_ptr=<value optimized out>) at runtime/platform/thread_linux.cc:85

­3 0x00000034d1407851 in start_thread (arg=0x7fe55cf10700) at pthread_create.c:301

­4 0x00000034d0ce894d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 3 (Thread 0x7fe55ef92720 (LWP 32564)):

­0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162

­1 0x0000000000461912 in dart::Monitor::Wait (this=0x7fff2ce50850, millis=0) at runtime/platform/thread_linux.cc:262

­2 0x0000000000415aee in Wait () at runtime/vm/thread.h:54

­3 dart::Dart_RunLoop () at runtime/vm/dart_api_impl.cc:1001

­4 0x000000000040b65b in dart::bin::main (argc=2, argv=0x7fff2ce50c08) at runtime/bin/main.cc:984

­5 0x00000034d0c1ecdd in __libc_start_main (main=0x40b850 <main(int, char**)>, argc=2, ubp_av=0x7fff2ce50c08,

    init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff2ce50bf8)
    at libc-start.c:226

­6 0x0000000000409979 in _start ()

Thread 2 (Thread 0x7fe55a3e5700 (LWP 6069)):

­0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216

­1 0x00000000004619cb in dart::Monitor::Wait (this=0x7fe550055000, millis=<value optimized out>)

    at runtime/platform/thread_linux.cc:267

­2 0x00000000006efe98 in Wait (this=0x7fe550055000) at runtime/vm/thread.h:54

­3 dart::ThreadPool::Worker::Loop (this=0x7fe550055000) at runtime/vm/thread_pool.cc:286

­4 0x00000000006effc5 in dart::ThreadPool::Worker::Main (args=140622866763776) at runtime/vm/thread_pool.cc:315

­5 0x0000000000462671 in dart::ThreadStart (data_ptr=<value optimized out>) at runtime/platform/thread_linux.cc:85

­6 0x00000034d1407851 in start_thread (arg=0x7fe55a3e5700) at pthread_create.c:301

­7 0x00000034d0ce894d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7fe558e20700 (LWP 6022)):

­0 0x00007fe5593a94e3 in ?? ()

­1 0xabababababababab in ?? ()

­2 0xabababababababab in ?? ()

­3 0xabababababababab in ?? ()

­4 0x000000000049ab30 in ?? () at runtime/vm/code_generator.cc:1026

­5 0x00007fe55cf51021 in ?? ()

­6 0x00007fe559988751 in ?? ()

­7 0x0000000000fe70d0 in ?? ()

­8 0x00007fe55aa98bf1 in ?? ()

­9 0x00007fe558e1e840 in ?? ()

­10 0x00007fe55b7657d9 in ?? ()

­11 0x00007fe55b765789 in ?? ()

­12 0x00007fe55b75ed89 in ?? ()

­13 0x00007fe55b75ed89 in ?? ()

­14 0x00007fe55cf51021 in ?? ()

­15 0x00007fe558e1e878 in ?? ()

­16 0x00007fe55aa2f2ba in ?? ()

­17 0x00007fe55b765789 in ?? ()

­18 0x00007fe55cf51021 in ?? ()

­19 0x00007fe55cf51021 in ?? ()

­20 0x00007fe559985531 in ?? ()

­21 0x00007fe5593a9269 in ?? ()

­22 0x00007fe558e1e8b8 in ?? ()

­23 0x00007fe559a8865c in ?? ()

­24 0x00007fe55cf51021 in ?? ()

­25 0x00007fe55cf51021 in ?? ()

­26 0x00007fe55cf51021 in ?? ()

­27 0x00007fe55cf51021 in ?? ()

­28 0x00007fe559984c61 in ?? ()

­29 0x00007fe559a885a9 in ?? ()

­30 0x00007fe558e1e8f8 in ?? ()

­31 0x00007fe559a884c6 in ?? ()

­32 0x00007fe55b762f19 in ?? ()

­33 0x00007fe55b762d99 in ?? ()

­34 0x00007fe55b761ca9 in ?? ()

­35 0x00007fe55b7632f9 in ?? ()

­36 0x00007fe5598052c1 in ?? ()

­37 0x00007fe559a883a9 in ?? ()

­38 0x00007fe558e1e9d0 in ?? ()

­39 0x00007fe5593bce0f in ?? ()

­40 0x00007fe55b762f19 in ?? ()

­41 0x00007fe55b762d99 in ?? ()

­42 0x00007fe55b761ca9 in ?? ()

­43 0x00007fe55b761ca9 in ?? ()

­44 0x00007fe55cf532a1 in ?? ()

­45 0x00007fe55cf51021 in ?? ()

­46 0x00007fe55b763269 in ?? ()

­47 0x00007fe55cf51021 in ?? ()

­48 0x00007fe55cf51021 in ?? ()

­49 0x00007fe55b7632f9 in ?? ()

­50 0x00007fe55cf51021 in ?? ()

­51 0x00007fe55cf51021 in ?? ()

­52 0x00007fe55b7632d9 in ?? ()

­53 0x00007fe55cf51021 in ?? ()

­54 0x00007fe55b761ca9 in ?? ()

­55 0x00007fe55cf532a1 in ?? ()

­56 0x00007fe55cf51021 in ?? ()

­57 0x00007fe55b763269 in ?? ()

­58 0x00007fe55997fa81 in ?? ()

­59 0x00007fe558e1e9d8 in ?? ()

­60 0x00007fe55b7632f9 in ?? ()

­61 0x00007fe55cf51021 in ?? ()

­62 0x00007fe55cf51021 in ?? ()

­63 0x00007fe5596c14f1 in ?? ()

­64 0x00007fe5593bc409 in ?? ()

­65 0x00007fe558e1ea68 in ?? ()

­66 0x00007fe559741887 in ?? ()

­67 0x00007fe55b7632d9 in ?? ()

­68 0x00007fe559a87621 in ?? ()

­69 0x00007fe55b763289 in ?? ()

­70 0x00007fe55cf51021 in ?? ()

­71 0x00007fe55b762f19 in ?? ()

­72 0x00007fe559981031 in ?? ()

­73 0x00007fe55b763269 in ?? ()

­74 0x00007fe55cf51021 in ?? ()

­75 0x00007fe55b763269 in ?? ()

­76 0x00007fe559981031 in ?? ()

­77 0x00007fe55a46d089 in ?? ()

­78 0x00007fe55ac66a61 in ?? ()

­79 0x00007fe559981971 in ?? ()

­80 0x00007fe55aa2e5a0 in ?? ()

­81 0x00007fe559a87b78 in ?? ()

­82 0x00007fe559544a91 in ?? ()

­83 0x00007fe5597417a9 in ?? ()

­84 0x00007fe558e1eac8 in ?? ()

­85 0x00007fe5594aa8f5 in ?? ()

­86 0x00007fe55b7632d9 in ?? ()

­87 0x00007fe55ac66a61 in ?? ()

­88 0x00007fe55cf51021 in ?? ()

­89 0x00007fe55ac66a61 in ?? ()

­90 0x00007fe55b7629a9 in ?? ()

­91 0x00007fe55b761c29 in ?? ()

­92 0x00007fe55b763289 in ?? ()

­93 0x00007fe55ac66a61 in ?? ()

­94 0x00007fe5596be871 in ?? ()

­95 0x00007fe5594aa509 in ?? ()

­96 0x00007fe558e1eb08 in ?? ()

­97 0x00007fe55948b9b6 in ?? ()

­98 0x00007fe55b762729 in ?? ()

­99 0x00007fe55b762619 in ?? ()

­100 0x00007fe55b762619 in ?? ()

­101 0x0000000000000000 in ?? ()

@lrhn
Copy link
Member

lrhn commented Jan 8, 2014

Added Area-VM, Triaged labels.

@DartBot DartBot added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Jan 8, 2014
@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
@zanderso
Copy link
Member

Assuming this is stale. Several customers have servers running for many weeks at a time without issues.

@zanderso zanderso added the closed-obsolete Closed as the reported issue is no longer relevant label Jun 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

4 participants