I need some general advice on how to prevent my VB6 application from
remaining in memory after it has supposedly shut down. I am still
trying to figure out why it does this, but I think it may be due to
incorrect error handling or some proper coding etiquette that I'm not
aware of. For example, I have seen it in memory after using the 'X' in
the top right corner to shut it down. Should I put something in the
Form_QueryUnload() subroutine to counter this? How about
Form_Unload(). Is it proper procedure to always code to these events?
My program uses a custom dll to talk to a camera, which I know can
cause grief, especially if the connection to the camera is not closed
before I end the application. I also use a MS Access database, but I
always close the connection right after I get the data I need. I only
do reads with this database.
I have spent some time researching how to detect another instance of
the application running, but App.PrevInstance isn't reliable and there
are other methods available, but I haven't tried them yet. My belief
is that it is better never to have a condition that would lead to the
application still running in memory when it shouldn't be.
If anyone has some advice on this topic, I'd appreciate it.
Re: Strange sudden shutdown issue with CF app ... Phone devices are notoriously low on virtual memory right out of the box because the OEMs decide to put every little thing into its own DLL and then have 25 processes launched at boot. ... Chris Tacke, Embedded MVP... We have created an app that basically connects to a web service gets data, then stores it locally on the device, and when a record needs to be modified/added the system first tries to connect the web server sees if its availible, if not then it stores in locally on the device until the connection comes back, now I noticed that if the device does not mess around with the data connection then the application sits nicely as long as its open, and never gets shut down. ... But again most of the time I get no exception at all but just simply disappears. ... (microsoft.public.dotnet.framework.compactframework)
Re: Not enough storage space ... I've tried to close the data source and the session,... When I close the connection, the code I use is this: ... This will actually release the memory or, as I experienced it, ...oledb Application ... (microsoft.public.sqlserver.ce)
Re: Strange sudden shutdown issue with CF app ... Phone devices are notoriously low on virtual memory right out of the box because the OEMs decide to put every little thing into its own DLL and then have 25 processes launched at boot. ... Chris Tacke, Embedded MVP... We have created an app that basically connects to a web service gets data, then stores it locally on the device, and when a record needs to be modified/added the system first tries to connect the web server sees if its availible, if not then it stores in locally on the device until the connection comes back, now I noticed that if the device does not mess around with the data connection then the application sits nicely as long as its open, and never gets shut down. ... But again most of the time I get no exception at all but just simply disappears. ... (microsoft.public.dotnet.framework.compactframework)
Re: Huge memory comsumption of ADODB Connection object ... Why I said the Connection... to nothing, the memory used by my app doesn't decrease, only when I close the ... I take the same opinion as you do, if the cursor doesn't return ... resultset to client, no impact will be imposed to client. ... (microsoft.public.data.ado)
Re: Socket BeginSend and disconnections ... It does depend somewhat on how the connection is broken and where. ... available memory before the network layer can detect the broken ... Is setting the socket buffer to 0 a non-default setting (right now we do not ... sense to catch all exceptions and try to continue gracefully if possible. ... (microsoft.public.dotnet.languages.csharp)
