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

Error with latest Heapsio(hashlink target) and Haxe 4.0.0-rc2 #4

Closed
shintiger opened this issue Jun 11, 2019 · 1 comment
Closed

Error with latest Heapsio(hashlink target) and Haxe 4.0.0-rc2 #4

shintiger opened this issue Jun 11, 2019 · 1 comment

Comments

@shintiger
Copy link

There are just one statement in main:
Executor.create(1);

Lock was aquired by another thread!
Called from hx.concurrent.lock.RLock.release (hx/concurrent/lock/RLock.hx line 201)
Called from hx.concurrent.atomic._AtomicInt.AtomicIntImpl.incrementAndGet (hx/concurrent/atomic/AtomicInt.hx line 158)
Called from hx.concurrent.$ServiceBase.__constructor__ (hx/concurrent/Service.hx line 56)
Called from hx.concurrent.executor.$Executor.__constructor__ (hx/concurrent/executor/Executor.hx line 19)
Called from hx.concurrent.executor.$ThreadPoolExecutor.__constructor__ (hx/concurrent/executor/ThreadPoolExecutor.hx line 40)
Called from hx.concurrent.executor.$Executor.create (hx/concurrent/executor/Executor.hx line 31)
Called from com.test.$ClientHeaps.main (com/test/ClientHeaps.hx line 28)
@sebthom
Copy link
Member

sebthom commented Jun 25, 2019

I could reproduce the issue and fixed it in the latest release 2.1.2. Thanks for reporting!

@sebthom sebthom closed this as completed Jun 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants