Memory Management Issue After Upgrading to FreeBSD 15

t4z3v4r3d

t4z3v4r3d

Hello everyone,

I recently upgraded my system from FreeBSD 14.2 to FreeBSD 15.0-CURRENT #2 stable/14-n269863-30bcbf8a2fef-dirty
and I've encountered a significant issue with memory management. Despite having 64 GB of RAM, the system seems to be consuming memory excessively and not releasing it properly.

Here are some details about the situation:

The system is running FreeBSD 15 , Hw : cpu AMD Ryzen 9 5900X . mem : 64 Gb ..
I have checked the processes using commands like top and htop, but I couldn't identify any specific application that is causing the high memory usage.
I have also looked into system logs (/var/log/messages and dmesg) for any errors or warnings, but I haven't found anything unusual.
I suspect that there might be an issue with kernel settings or memory management configurations.
Has anyone else experienced similar issues after upgrading to FreeBSD 15? Any suggestions or solutions would be greatly appreciated.

Thank you!
 
Why run a highly unstable developer version when you obviously can't handle it? You should keep this forum rule in mind:

DutchDaemon

Thread 'Topics about unsupported FreeBSD versions'

The FreeBSD Forums cater primarily to end-users and systems administrators. As such, the Forums focus almost exclusively on FreeBSD versions that are officially supported according to the official FreeBSD website. Since resources are scarce, the FreeBSD Forums strongly suggest that anyone asking questions on the forums run one of the officially supported versions (see the links at the end of this post), for which the installed user base is logically the broadest.

In terms of 'unsupported versions' we make the following distinction:

  1. FreeBSD versions that are...
  • Thanks
  • Like

... not to mention check up on /usr/src/UPDATING. The idea of releasing versions like these is to allow people to test things out and then report their findings; where it's kinda expected to try and come up with some kind of a solution. Remember, development version?

As for the rule I quoted... development is on-going, changes and such are a daily thing. For all I know you ran into a hiccup which could already been spotted & addressed 30 minutes ago... there's just no use in even trying to help you out because if this were true then I'm basically wasting my time. And your solution would be to rebuild & reinstall.

And the memory? What's wrong with using memory in the first place? That's what it's for, not to mention that CURRENT has a ton of debugging features enabled, those are definitely going to gobble up resources.
 
Thank you for your response. First of all, I believe that this forum could be a way to report issues with the development version. If it isn't, I apologize and must have made a mistake!

Secondly, I have been using this system for a long time and I want it to always be in the best condition. Therefore, whenever I find an error or issue, I would like to report it and have it resolved. I think this is a matter of personal preference; some people might prefer to keep these problems hidden.

Thirdly, this is my first time using the development version, and I would like to be part of the development process or at least observe it. If you don't want to respond, that's fine. There’s no need to ask why I’m using it or whether I have the ability to use it; that is a personal matter, and I am interested in reporting any issues I see, as it might be helpful.

You can simply respond without addressing my ability or inability to use it.

In any case, I will not report any more issues. It seems that your capabilities are very extensive, and I am discussing this with the creator of FreeBSD.

I ran a version of Ollama on this machine. After running it, while I was working, the system crashed and rebooted. To test again, I performed the same actions. I checked the temperature, voltage, and other parameters. When the memory usage reached about 60 gigabytes, the system crashed again, even though I had closed Ollama after a while and no additional programs were running. However, memory usage continued to grow.

I checked, and there were no instances of Ollama running, but memory was still increasing. Konsole was consuming the most memory here, around 48 gigabytes. Even after killing the Konsole process, the memory allocated to it was not freed and remained in the same state. This is what happened.
 
t4z3v4r3d said:
I ran a version of Ollama on this machine. After running it, while I was working, the system crashed and rebooted. To test again, I performed the same actions. I checked the temperature, voltage, and other parameters. When the memory usage reached about 60 gigabytes, the system crashed again, even though I had closed Ollama after a while and no additional programs were running. However, memory usage continued to grow.
Click to expand...

Please don't say "crashed". What specifically happened? Kernel panic?

Konsole was consuming the most memory here, around 48 gigabytes. Even after killing the Konsole process, the memory allocated to it was not freed and remained in the same state. This is what happened.
Click to expand...

That doesn't make sense. How do you know that? If you killed the process you cannot display its memory usage anymore.


I ask again: do you actually see symptoms of memory overload such as slowdown while paging out?
 
You must log in or register to reply here.
Back
Top