# FMOD\_ERR\_MEMORY value of FMOD\_RESULT returned when calling set3DAttributes(...)
**URL:** https://qa.fmod.com/t/fmod-err-memory-value-of-fmod-result-returned-when-calling-set3dattributes/13669
**Category:** FMOD Studio
**Created:** [January 26, 2018, 4:00pm UTC](https://qa.fmod.com/t/fmod-err-memory-value-of-fmod-result-returned-when-calling-set3dattributes/13669 "2018-01-26T16:00:58Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@adamsporka](https://qa.fmod.com/u/adamsporka)
#### Post date: [January 26, 2018, 4:00pm UTC](https://qa.fmod.com/t/fmod-err-memory-value-of-fmod-result-returned-when-calling-set3dattributes/13669/1 "2018-01-26T16:00:58Z")
Hello all,
I was wondering if I could ask for help. I have been trying to figure out why the following behavior happens:
FMOD runs in our title for several hours with thousands of events, CreateSounds, streamed audio, snapshots, all that. At some point, quite rarely (say once every 500 hours), when calling set3DAttributes on an event instance, I get FMOD\_ERR\_MEMORY for an FMOD\_RESULT of the operation. At that point, FMOD Studio practically ceases to work. The playback is stuck in an endless loop approx. 0.8 seconds long.
// m\_pFmodStudioEventInstance points to a valid object
// m\_Pos is a valid object
FMOD\_RESULT result = m\_pFmodStudioEventInstance-\>set3DAttributes(&m\_Pos);
FMOD Studio would have by then allocated about a half of the pool available to it but still it should have plenty of memory to work. I was never able to reproduce the error.
My version is 1.09.04. An old one, I know, but for certain reason we can’t really upgrade.
Please, have anyone encountered a similar thing? What would you do?
Thanks much,
Adam
---
### Author:  [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [January 29, 2018, 5:54am UTC](https://qa.fmod.com/t/fmod-err-memory-value-of-fmod-result-returned-when-calling-set3dattributes/13669/2 "2018-01-29T05:54:19Z")
I can’t say we have encountered this particual issue but FMOD\_ERR\_MEMORY normally means “Not enough memory or resources.”.
Unfortunately without a repro or any more info we couldn’t even guess at what could be the cause.
---
### Author:  [@adamsporka](https://qa.fmod.com/u/adamsporka)
#### Post date: [February 4, 2018, 7:31pm UTC](https://qa.fmod.com/t/fmod-err-memory-value-of-fmod-result-returned-when-calling-set3dattributes/13669/3 "2018-02-04T19:31:19Z")
Thanks! Yeah, I’m trying to find a reliable repro for days now. I have learned how to “break” the engine in various ways but none ends up with the same symptoms 🙂
---
### Author:  [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [February 5, 2018, 12:17am UTC](https://qa.fmod.com/t/fmod-err-memory-value-of-fmod-result-returned-when-calling-set3dattributes/13669/4 "2018-02-05T00:17:43Z")
> [@](#):
>
> Thanks! Yeah, I’m trying to find a reliable repro for days now. I have learned how to “break” the engine in various ways but none ends up with the same symptoms 🙂
As a bit of a test, if you can test it with a newer version of 1.09 (eg. 1.09.11) and the issue is fixed, we might be able narrow down the cause.
Also feel free to send a log file to [support@fmod.com](mailto:support@fmod.com) if you can capture the issue.