Possible bug: Can't close Untitled.exe sometimes

[STxAxTIC]

Glad someone like bplus is seeing eye to eye with me on this.  Anyway, if it helps get closer to the problem, I can say a few things about the conditions leading to when it happened.

Besides the obvious (Win10, qb64v1.4 candidate, no AV, no, FW)

0. "Failure to close", to me right now, is defined as the program ending properly, getting the "Press any key" message, but then the X button and alt+f4 each fail to dismiss the window.

1. I was in the edit > run > edit > run etc. phase of finishing a program at each occurrence.

2. I never, or very rarely at least, have multiple instances of Qb64 open. Nor do I have the source open in another editor. No exceptions to this were going on when the programs failed to close.

3. Item 2 extends to my whole habit on the computer. Everything is closed, including browers and tabs, daily. I probably had Chrome open, maybe a folder or two, when it happened.

4. I havent made any changes to my system whatsoever beyond view settings when I bought the thing.

[bplus]

Ah, I am running v1.3 standard issue most the time when I hang a screen. I have no idea the exact stat but 1 time in 500, 1 time in 1000?  Certainly 1 time in 100 seems too frequent.

PS I did not notice correlation to "untitled", I would say I am deep into mod and test, mod and test a titled and folder saved bas file. I will be sure to take more notes of such events but it is usually when I am in the middle of blundering my way into something interesting. :)

[Pete]

I've had this happen maybe once or twice with v.1.3, say over several hundreds of times running exe programs. I just go to task manager and close it there, no biggie, but to the point, my gut feeling was it was caused by some OS interference, not QB64. I do recall I had a bunch of things going on (windows open, several apps running, etc.)

Pete

[FellippeHeitor]

I get it a lot on a Windows 7 system with lots of admin stuff that prevent users from doing anything to system's settings. God knows how many processes it has running just to prevent me from using it normally.

That's far from STx's case though. This is a hard one to track down.