0
0

Hi everyone! First post here, be gentle!

I’ve seen other people mentioning similar problems in passing, but I couldn’t find anyone directly refering to the following issue.

Basically after I’ve called FSOUND_Init, I have to call FSOUND_Close before the process ends or else the VB IDE dies with the following message:

[quote:2kwq8qo5]VB5.exe – Application Error
The instruction at “0x…..” referenced memory at “0xsameasbefore”. The memory could not be “read”.[/quote:2kwq8qo5]

This is a problem when some other issue with the application causes me to end the application’s execution early – thus not giving me the opportunity to call FSOUND_Close.

Is this a problem with VB or VB5 in particular? Is there anything I can do to help mitigate this probem?

Thanks guys! ๐Ÿ˜‰

  • You must to post comments
0
0

You just need to close fmod before stopping your program :)

You can either always compile your program and then start it, or, the way I do it for debugging:
I have one function called ‘ExitApp’ that will make sure everything is closed and unloaded.
When you want to debug, and you have some error, you should always be able to type ‘ExitApp’ in the Immediate Window.
This will stop your application safely.

  • You must to post comments
0
0

Ahh – good idea. Yes of course, I just have to remember to call FSOUND_Close myself from the immediate window.

That works well, thanks! ๐Ÿ˜›

  • You must to post comments
0
0

when debuggin an app in VB it runs as part of VB

so stuff loaded by the app can be left loaded in VB long after the app is gone with bad results

this is very different from delphi where you app is a seperate process even though it is under the control of the integrated debugging environment

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.