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

Jump to bottom

VM Segmentation fault when specifying too large object heap #13744

Closed
larsbak opened this issue Oct 2, 2013 · 0 comments
Closed

VM Segmentation fault when specifying too large object heap #13744

larsbak opened this issue Oct 2, 2013 · 0 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-cannot-reproduce Closed as we were unable to reproduce the reported issue type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@larsbak
Copy link

larsbak commented Oct 2, 2013

Using the 32bit version Dart VM
$ dart --old_gen_heap_size=2048 fisk.dart
Segmentation fault (core dumped)
Please add code to validate the specified heap size instead of core dumping.

Here is another angle on the same bug:
$ export DART_VM_OPTIONS=--old_gen_heap_size=2048 --new_gen_heap_size=32
$ dart2js
Segmentation fault (core dumped)
@larsbak larsbak added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Oct 2, 2013
@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
@zanderso zanderso added the closed-cannot-reproduce Closed as we were unable to reproduce the reported issue label Jan 5, 2017
@zanderso zanderso closed this as completed Jan 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-cannot-reproduce Closed as we were unable to reproduce the reported issue type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kevmoo @larsbak @zanderso