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

Crash in VM in dart::Api::NewLocalHandle #591

Closed
sgjesse opened this issue Nov 24, 2011 · 4 comments
Closed

Crash in VM in dart::Api::NewLocalHandle #591

sgjesse opened this issue Nov 24, 2011 · 4 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.

Comments

@sgjesse
Copy link
Contributor

sgjesse commented Nov 24, 2011

I have seen a crash with this stack a couple of times while testing (in release mode).

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf15bfb70 (LWP 12496)]
dart::Api::NewLocalHandle (object=...) at ../runtime/vm/dart_api_impl.cc:97
97 LocalHandle* ref = local_handles->AllocateHandle();
(gdb) bt

­0 dart::Api::NewLocalHandle (object=...) at ../runtime/vm/dart_api_impl.cc:97

­1 0x08056313 in dart::Api::ErrorFromException (obj=...)

    at ../runtime/vm/dart_api_impl.cc:181

­2 0x08059d88 in dart::Dart_HandleMessage (dest_port=7116, reply_port=0,

    dart_message=0xf11004c0) at ../runtime/vm/dart_api_impl.cc:621

­3 0x08081f67 in dart::Isolate::StandardRunLoop (this=0x82bc750)

    at ../runtime/vm/isolate.cc:252

­4 0x0814c17e in dart::RunIsolate (parameter=137092312)

    at ../runtime/lib/isolate.cc:206

­5 0x080f2bf8 in dart::ThreadStart (data_ptr=0x82bdd00)

    at ../runtime/vm/thread_linux.cc:67

­6 0xf7fab96e in start_thread (arg=0xf15bfb70) at pthread_create.c:300

­7 0xf7c84b5e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Backtrace stopped: Not enough registers or memory available to unwind further

@a-siva
Copy link
Contributor

a-siva commented Nov 28, 2011

Do you have a test that reproduces the problem?

@iposva-google
Copy link
Contributor

If you do not have a reproducible test case, can you please let us know about the circumstances under which you are hitting these? Thanks!


Set owner to @sgjesse.
Added Accepted label.

@turnidge
Copy link
Contributor

I've built a unit test that reproduces the problem, I think.


Set owner to @turnidge.

@turnidge
Copy link
Contributor

Should be fixed in bleeding_edge, revision 1904.


Added Fixed label.

@sgjesse sgjesse added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. labels Nov 29, 2011
nex3 pushed a commit that referenced this issue Aug 31, 2016
This issue was closed.
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, and the AOT and JIT backends.
Projects
None yet
Development

No branches or pull requests

4 participants