Guilherme Bernal

I'm also affected by this. Happened today after I upgraded all packages (from about 1 month ago). Not sure about the exact cause. Typescript 2.3.0-RC also cause this.

Looks like this was fixed by pull https://github.com/Microsoft/TypeScript/pull/15075, issue https://github.com/Microsoft/TypeScript/issues/14628. Will be released as TS 2.3.1 soon.

I can reproduce in 2.3.1 as well, but not with `typescript@next`. The fix was *NOT* released, but resides in master for 2.4.0. They really should release this.

I think we are being hit by different bugs with equal behavior them.

This PR from the Crystal compiler seems to fix this issue: https://github.com/crystal-lang/crystal/pull/11739

Hi @drhuffman12! I opened a PR that will fix this. Please take a look: https://github.com/anykeyh/crystal-coverage/pull/18

I'm using it like this: From your project modify `shard.yml` to include: ```yml development_dependencies: coverage: github: lbguilherme/crystal-coverage ``` Install with: shards install Then run specs with coverage using: bin/crystal-coverage

Hi @erdnaxeli! I opened a PR that will fix this. Please take a look: https://github.com/anykeyh/crystal-coverage/pull/18

- https://github.com/veelenga/ameba redirects to https://github.com/crystal-ameba/ameba, so the two are exactly the same and there is no visible difference for the user. The legacy name is supported. - shard.yml is not...

Bug: If an `IsolateHandle` is created with `v8::Isolate::new_handle`, the underlying isolate is never dropped because `drop_annex` is never called and the `Arc` has a cycle. Additionally, there is no way...