Page 1 of 1
CMD+Quit - PB hangs
Posted: Tue Apr 08, 2025 3:22 pm
by SparrowhawkMMU
I'm not sure whether this is a problem unique to myself or not, but I've noticed that since upgrading* macOS to Sequoia 15.4 (24E248), CMD-Q hangs PB after which I have to force quit it via the Finder. Using the Quit menu item in the main PB menu however exits cleanly without error.
This happens consistently, ie it's not a one off or occasional issue.
MacBook Pro M3 Max 36GB
PureBasic 6.20 - C Backend (MacOS X - arm64)
IDE build on 02/12/2025 [15:42] by fred
Branch: v6.20 Revision: 29c61098c686
* I think it's only since I upgraded to macOS 15 a few days ago, but I've not opened PB for a while so perhaps it's also true in macOS 14.x?
Re: CMD+Quit - PB hangs
Posted: Tue Apr 08, 2025 3:48 pm
by mrbungle
I have have seen this recently as well. For me, it seems to happen when I have no source code loaded. Happens only in the IDE and requires a force-quit.
Re: CMD+Quit - PB hangs
Posted: Tue Apr 08, 2025 3:53 pm
by Fred
could you try to disable 'session history' to see if it's related ?
Re: CMD+Quit - PB hangs
Posted: Tue Apr 08, 2025 8:15 pm
by mk-soft
It is not related to the session history.
CMD-Q still hangs.
Perhaps change to PostEvent(#PB_Event_CloseWindow, #WINDOW_Main, 0) of #MENU_Exit
Re: CMD+Quit - PB hangs
Posted: Wed Apr 09, 2025 10:35 am
by SparrowhawkMMU
I can confirm what mk-soft has already stated, that disabling the session history has no effect.
Another problem occurred as I was testing this - I opened PB on my built in screen, opened the Settings form and dragged it onto my main monitor (I have 1 external monitor linked via HDMI on a USB hub) - the settings page when dropped onto the target immediately disappears and cannot be retrieved. There are no other windows on that desktop, so not hidden.
Long clicking on the PB icon in the Dock and choosing show all windows does show the settings page in the dashboard view, but selecting it immediately hides it again. At which point closing PB hangs, even with the File->Quit route. This new issue I can replicate every time too.
Would you like me to raise a separate thread for this?