Closed rcoreilly closed 7 months ago
Looks like it might be stuck in a mutex hang around the rendercursor in texteditor.
we were not even deleting the window contents -- now doing that, and destroy closes the cursor -- looks like it is fixed. will reopen if recurs.
this is now happening semi-reliably (but not exactly reproducible). things look like they are in some kind of zombie-like state when I debug attach. maybe some recent goosi / event loop change for testing stuff? @kkoreilly ?
I don't think I have done anything recently that could have caused this.
I added more direct route to turning off cursor which seemed to be the problem - now working
yep, happening again: just caught one in the act -- waiting on the texteditor.ViewBlinker channel (just renamed to EditorBlink*) in texteditor/cursor.go -- need a quit cleanup call..
also for same thing in textfield
Fixed in c129af4.
its baaak... definitely happening.
My simulations in axon are now 100% reliably not closing.
furthermore, I can verify that a build from 2/14 did close (immediately after starting), while the same thing built now fails to quit. thus, it was a relatively recent change
@kkoreilly this is happening in demo too. please fix.
if you close all the windows in an app, the app itself should quit, due to the wait condition. this often, but not always, happens.