Skip to content

Dart VM crash (Access Violation) on Windows (1.12.1) #28757

Closed
@DanTup

Description

@DanTup

While working on some code today using built_value I managed to get the Dart VM to crash (that is, Windows said dart.exe has encountered a problem and had to close rather than the normal exception spat to screen).

I was able to reduce the code to this very small sample:

import 'dart:async';

Future main() async {
  await doThing("test");
}

doThing<T>(String request) async {
  var a = new FullType(T);
}

class FullType {
  FullType(a);
}

When I run this, the VM crashes. I don't think this code logically makes much sense (I don't even know if Generics are supposed to work yet, and there's a mismatch of awaits and non-async code) but it doesn't seem like the VM should crash.

Most tweaks I try to simplify/correct the code stop the crash from occurring.

If I hit Debug in the Windows dialog I get the following information:

Unhandled exception at 0x00007FF60461094A in dart.exe: 0xC0000005:
Access violation reading location 0x0000000000000010.

I'm on Windows 10 Pro x64 running v1.21.1 of the SDK. I have the above code in a .dart file and I'm just running it with dart myfile.dart.

Dart crash

Metadata

Metadata

Assignees

Labels

area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions