# High Memory Usage

**URL:** <https://forum.fxsound.com/t/high-memory-usage/825>\
**Category:** Get Help\
**Created:** [May 15, 2022, 7:40am UTC](https://forum.fxsound.com/t/high-memory-usage/825 "2022-05-15T07:40:46Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Audiofile](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@Audiofile](https://forum.fxsound.com/u/Audiofile)\
**Post date:** [May 15, 2022, 7:40am UTC](https://forum.fxsound.com/t/high-memory-usage/825/1 "2022-05-15T07:40:46Z")

</div>

![High Memory Usage](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/1X/cc6a054dfb61b15f464401a6207911f95ce47bfe.jpeg)

Hi there,

I have been using the latest version of the program (1.1.14.0) on Windows 7 (64 bit) running 4 GB RAM. I have noticed an unusually high memory usage on my PC as seen in the attached screenshot.

Mostly tends to happen when I leave the PC locked for a long time / multiple users use the PC (multiple accounts).

Please fix.

---

<div class="post-metadata">

**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\
**Post date:** [May 15, 2022, 10:09am UTC](https://forum.fxsound.com/t/high-memory-usage/825/2 "2022-05-15T10:09:30Z")

</div>

Hello, and welcome.  
First of all, please refer to this thread:

> [@High CPU usage when using FxSound](https://forum.fxsound.com/t/high-cpu-usage-when-using-fxsound/488):
>
> hi there. I really like this app the interface is very nice and sound is good. but CPU is always on +20% usage when Fxsound is enabled. Am the only one who has this issue? windows 10 , intel 2500k core i5

---

<div class="post-metadata">

**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\
**Post date:** [May 15, 2022, 10:14am UTC](https://forum.fxsound.com/t/high-memory-usage/825/3 "2022-05-15T10:14:31Z")

</div>

Secondly: what kind of fix were you expecting?  
This issue could be taken into account when programming the next version of the program.  
Fixing the issue on your machine long-distance, however, is very different…

---

<div class="post-metadata">

**Author:** ![Dolmatov](https://avatars.discourse-cdn.com/v4/letter/d/d26b3c/32.png) [@Dolmatov](https://forum.fxsound.com/u/Dolmatov)\
**Post date:** [May 16, 2022, 2:02am UTC](https://forum.fxsound.com/t/high-memory-usage/825/4 "2022-05-16T02:02:30Z")

</div>

> [@Audiofile](#):
>
> the latest version of the program (1.1.14.0)

What?

## 1.1.15.0 [Release Version 1.2.3.0 · fxsound2/fxsound-app · GitHub](https://www.fxsound.com/changelog)

## 1.1.15.6 (beta) [The topic](https://forum.fxsound.com/t/beta-announcement-fxsound-language-options/264)

---

<div class="post-metadata">

**Author:** ![PLEASE\_DELETE](https://avatars.discourse-cdn.com/v4/letter/p/dec6dc/32.png) [@PLEASE\_DELETE](https://forum.fxsound.com/u/PLEASE_DELETE)\
**Post date:** [May 16, 2022, 11:16am UTC](https://forum.fxsound.com/t/high-memory-usage/825/5 "2022-05-16T11:16:29Z")

</div>

I would advise to first uninstall and try the latest version 1.1.15.0 and download it here from the official page and retry.

Also make sure that your Windows and especially sound hardware drivers are updated to the very latest version aswell.

When the issues persists, let us know.

---

<div class="post-metadata">

**Author:** ![Audiofile](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@Audiofile](https://forum.fxsound.com/u/Audiofile)\
**Post date:** [May 17, 2022, 12:37pm UTC](https://forum.fxsound.com/t/high-memory-usage/825/6 "2022-05-17T12:37:50Z")

</div>

Thanks! I did check that but it is the high memory usage in my case and not the CPU usage as seen in the screenshot. Anyway, I see that a new version was already out but sadly the program did not notify me of new updates - something that should be considered by the developers if not already implemented.

Coming to your second post, the expectation is for the developers to re-look at the code and optimize it for the PC configuration as the issue is not at my end but with the program.

---

<div class="post-metadata">

**Author:** ![Audiofile](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@Audiofile](https://forum.fxsound.com/u/Audiofile)\
**Post date:** [May 17, 2022, 12:38pm UTC](https://forum.fxsound.com/t/high-memory-usage/825/7 "2022-05-17T12:38:42Z")

</div>

Thank you for letting me know. It would have been great if the program informs the users about the latest updates.

---

<div class="post-metadata">

**Author:** ![Audiofile](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@Audiofile](https://forum.fxsound.com/u/Audiofile)\
**Post date:** [May 17, 2022, 12:39pm UTC](https://forum.fxsound.com/t/high-memory-usage/825/8 "2022-05-17T12:39:24Z")

</div>

Yes, that is something I will do and let you know if the issue persists. Thanks!

---

<div class="post-metadata">

**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\
**Post date:** [July 8, 2022, 8:11pm UTC](https://forum.fxsound.com/t/high-memory-usage/825/9 "2022-07-08T20:11:53Z")

</div>



---

<div class="post-metadata">

**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\
**Post date:** [December 10, 2023, 1:42pm UTC](https://forum.fxsound.com/t/high-memory-usage/825/10 "2023-12-10T13:42:44Z")

</div>


