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

VM Crash: Integer shift behaves unexpected #16633

Closed
DartBot opened this issue Feb 7, 2014 · 4 comments
Closed

VM Crash: Integer shift behaves unexpected #16633

DartBot opened this issue Feb 7, 2014 · 4 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 needs-info We need additional information from the issue author (auto-closed after 14 days if no response) type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@DartBot
Copy link

DartBot commented Feb 7, 2014

This issue was originally filed by mugadr.m@gmail.com


What steps will reproduce the problem?
I havent found a way to reproduce the error in a new project, but this is the code the error appears (see information below for different versions):
http://pastebin.com/LCN7afVc (lines 64 to 68)

What is the expected output? What do you see instead?
No output. I get a crash in dartium 'Aw, snap! Something went wrong while displaying this webpage.'. No exception is thrown (even with dart editor set to break on all exceptions).

What version of the product are you using? On what operating system?
Dart Editor 1.1.1, Dart SDK 1.1.1

Please provide any additional information below.
Essentially the problem could have been narrowed down the following line:
int a = 0xFF;

If i use this the browser crashes. If i use int a = 0xFF.toInt(); it all works well. Also if I use something like int a = 63; everything is fine. But as soon as a is > 63 dartium/chromium crashes. Adding a toInt() solves the problem.

I could send the entire project but id like to not post it in public. I'll also try to reproduce the error in another project.

@DartBot
Copy link
Author

DartBot commented Feb 7, 2014

This comment was originally written by mugadr.m@gmail.com


Something I forgot in the addition information:
If I use the code posted above and set a breakpoint on line 63 which gets hit in the first execution of the loop and remove it when it gets hit the first time it also works with any given value.

@lrhn
Copy link
Member

lrhn commented Feb 7, 2014

Added Area-VM, Triaged labels.

@lrhn
Copy link
Member

lrhn commented Feb 7, 2014

Changed the title to: "VM Crash: Integer shift behaves unexpected".

@iposva-google
Copy link
Contributor

The code in the pastebin is not runnable so it is hard to reproduce on our side and thus we have no information to go on. There were significant stability fixes in 1.1.2, so please update and report whether this addresses your issues.


Added NeedsInfo label.

@DartBot DartBot added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. needs-info We need additional information from the issue author (auto-closed after 14 days if no response) labels Feb 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
@mhausner mhausner added the closed-obsolete Closed as the reported issue is no longer relevant label Jun 21, 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 needs-info We need additional information from the issue author (auto-closed after 14 days if no response) type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

5 participants