A long time to close the execution window

[krovit]

Good morning everyone!

I see that it is still the forum and development of QB64... Very well!  I am so pleased that this wealth of knowledge is not being dispersed.

I've taken up some of my projects... and something has to be changed but maybe it depends on the operating system (I still seven but who knows what hidden updates it has suffered... 7 poor...)

The first question is this: when the execution ends with the END command (and even when the program ends) now it takes a long, long time to close the window (even clicking on X of the windows window), before the closing was instant!

How about that?
Thank you!

P.S.
It seems to me that the [abandoned, outdated and now likely malicious qb64 dot net website - don’t go there] forum, which contained so much information, has been permanently lost. It's true?

[Petr]

Hi.

 I do not have the slightest speed issue under Windows 7 when closing applications using the END and or SYSTEM commands.
But my system has other bugs that are fortunately not related to QB64. But I have the best security precautions - an empty computer. :)

Unfortunately, this with [abandoned, outdated and now likely malicious qb64 dot net website - don’t go there] is true. Read Galleon's alert here https://www.qb64.org/forum/index.php?topic=1913.0

[krovit]

Thank you for the answer.

The problem persists and is quite annoying (I also tried to change the windows registry by decreasing the allotted time to terminate the programs, but with no appreciable results).

I'll also make a few more reports because QB64, unexpectedly, now responds differently (and I still use the version I used almost a year ago).

Finally, we hope that with the termination of support to Seven Microsoft does not force us to deposit (our) apps at its repository as it had expressed its desire to do months ago... worth not running on Windows 10 the program so laboriously built...

[Petr]

Well, for me, to improve my knowledge, I would definitely prefer to switch to Linux instead of Windows 10. Mainly because I totally refuse to support Microsoft's policy.

To solve your problem. First, try the behavior of the latest version of QB64. Do you have a program on your system, such as an antivirus, or a real-time data compression program that could cause this behavior? What about other apps? Do they behave the same or do they close now? Do you have QB64 installed on the system disk or another disk? I have QB64 on a disk with no operating system. If nothing helps, can you try a system restore point on an earlier date?

Maybe .... what to try to uninstall the latest updates?

[krovit]

Hi Petr

I'll try on a dedicated machine.

It may also depend on the amount of space left on the harddisk (now it's a little bit).

[krovit]

Hi Petr

maybe I've identified the cause of the problem.

I think it's the "Toolwiz Time Freeze" program, a very useful application (and free for personal use) to restore the operating system or part of it in case of need.

Apparently it interferes heavily with applications created by QB64, especially with the slightly more complex ones.
If the program is disabled, it exits immediately. Anyway, I'm going to keep trying to understand if this is always true (???)

Thanks for the tips! I tried the application in SandBoxie and from there I understood how to proceed.

I think it's helpful that it's made known to everyone.

Thank you!