Re: My Gambas programs do not close any more

[gbWilly <gbWilly@xxxxxxxxxxxxxx>]

On Sunday, January 26th, 2025 at 21:12, Christof Thalhofer <chrisml@xxxxxxxxxxx> wrote:

> Am 26.01.25 um 18:05 schrieb Benoît Minisini:
>
>
>
> The last thing it does is 'Form_Close()' where I let it print "stopped"
> which it does and then it stalls ... with 3.19.6 and with 3.20.1 ...
> only on my main machine, not in the VM ... crazy.
>
> It uses some of my Gambas libs, maybe I did sth wrong, I'll keep trying.

Hi,

The gambas libs reference reminds me of an ongoing problem I have run into since running one of my applications in gambas 3.18.4 (end 2023). I didn't bother reporting on it as I figured it must be something on my site, but your report (and linking it to using gambas libraries in the application), might make it a bug (or not).

I sometimes (I still did not figure out under what circumstances) have one of my applications not close properly when running it from IDE during development and it also uses gambas libraries. The run button in IDE is not clickable and I need to actually click the stop button to actually close the application. I also use Form_Close code to close databases, remove temp folders etc. As it does not always happen, have been trying to keep in mind in what order I do stuff when it happens, but still not solved the issue or tracked where it might occur. And it only happened when running the application from the IDE so far.

Today, I closed the installed version of this application (so NOT run from IDE) and it closed just fine. After about 30 sec. to a minute after it was closed I got an error pop-up referring to code in a class in the library! Strange, because the application that uses the library had been closed. The gambas library wanted to return something to application, but the application seems to be already closed and not accepting library feedback. So, was my application actually really closed or just part of it? The visual part was closed (or at least no longer visible), but apparently there was still something related to application (in the library in this case) running.

Since this all happened when closing all off before going home I didn't bother further investigating. Could it be that upon closing an application, processes that are run by the gambas libraries are NOT ALWAYS closed, because they are still doing their thing? My code in library is a socket client class that seems to have received something from the other end although I closed my connection to it before closing the application.

I've been working with gambas written socket server/clients for over 10 years now to manage remote systems on intranet and I have never had this problem until I bumped gambas to 3.18.4 at work end 2023.
Anyway, I will be keeping an eye open to see if I can pin point where stuff goes wrong.


gbWilly

BTW I'm running this at work in gambas 3.18.4, so I can't provide a project and as I do not know what is causing it I can't replicate it in a test project. It only happens once so often, so it is a bit of an exceptional case .