I have a problem with the latest version of Fmod. It works fine on OS X, however the same executable on OS 9.2 gives an “unmapped memory exception error” inside of FSOUND_Memory_Pool_Free. The call stack looks like this:
Looking at the pointers tells me that FMOD is attempting to unallocate some memory that has not been allocated. Question I have is, Am I doing something wrong to cause this?
Has anyone else run accross a problem like this?
For the record, this is happening in the initialization of FMOD when I call the following code line:
Thanks for any info.
- slntnsnty asked 13 years ago
You are right in saying the issues are completely different. Sorry. But my origianl posting was on a runtime memory issue in OS9. Then I ran some example files and got linking problems (in OS9). Moved to building in OSX and examples worked….except the use of Stream_Open()..which reports as a link error. I was curious if the same probelm was happening elsewhere. I’ll try keep these two issues seperate.
Yea, i have had a similar problem (see Mac/CW FMOD 3.73 memory Error). Also having a link error when using Open_Stream(….) in OSX! .
Memory problem (__pool_free) only occurs when developing in OS9.
Bret assured me that code compiled and worked on their machine. I still need to do some boring checking on things, os9 builds etc. swapping between systems….. 😥
My opinion, there may be a small bug due to completely different memory strategies between systems. Therefore, a special build is needed for os9. This is all a bit new to me. All previous work i’ve done before this has worked on both os’s.
up-shot……you are not alone.
Please login first to submit.