-
Notifications
You must be signed in to change notification settings - Fork 9
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
Creating a spawn blocks application closure #37
Comments
What does |
I'm on |
@Araq all imports
...
niup.open()
all variable and callback definitions
...
main_window.showXY(IUP_CENTER, IUP_CENTER)
niup.mainLoop()
niup.close()
malebolgia.panicStop() # <- THIS HANGS FOREVER!
echo "END" Added echo's into the proc panicStop*() =
## Stops all threads.
echo 1
globalStopToken.store(true, moRelaxed)
echo 2
joinThreads(thr) # <- HANGS HERE!
echo 3
deinitCond(chan.dataAvailable)
echo 4
deinitCond(chan.spaceAvailable)
echo 5
deinitLock(chan.L)
echo 6 |
@Araq |
Pretty sure it's something else, |
Hey @Araq P.S.: |
Yeah well, you need to setup WSL and run it via valgrind under Linux. Most likely one of your dependencies doesn't play nice and it's the most reasonable way to debug these things. |
Hi,
I have a niup application that uses
malebolgia
tospawn
a sound effect in a{.cdecl.}
callback. This is the callback:Now, running the application and closing it without the callback
countdown_tick
not being executed: no problems, application closes.But running it and executing the callback, everything is fine, the
soundutils.play_wav
spawning works great and "Sound playback completed." is echoed, but closing the application echo's "Application closed." and then hangs indefinitely, untilCtrl+C
is pressed.If I change the callback to a synchronous execution, like so:
... it also works without problems.
Any ideas of what's blocking the closing of the application when a
spawn
is created?P.S.:
I tried adding
malebolgia_master.cancel()
at the end after the echo, no difference.Also tried malebolgia.panicStop(), but that call itself also hangs indefinitely.
The text was updated successfully, but these errors were encountered: