Memory leak with no actions at all. #100505

New Issue

Rodrigo Couto · 2022-08-19T18:48:12+02:00

Rodrigo Couto commented

2022-08-19 18:48:12 +02:00

System Information
Operating system: Linux-5.13.0-44-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01

Blender Version
Broken: version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: bcfdb14560
Worked: version: 2.93.9, branch: master, commit date: 2022-04-19 14:25, hash: 31712ce77a

Short description of error
I just open any version of Blender since 3.0 and just moving the mouse around makes the amount of memory used by Blender rise. It doesn't stop. It doesn't liberate the memory, ever. It just goes higher and higher, until the memory is full. At first, I thought it was something related to the projects and operations I was doing. I tried to reduce the undo steps and everything else that's advised to reduce memory consumption, and today I realized that simply moving the mouse around was already increasing the memory usage of Blender. I don't need to do any actions

Now, I have two versions of Blender open, to compare 2.93.9 and 3.2.2. Both have the same scene: Susanne, a camera, and a point light. At first, Blender 3.2.2 started with a smaller amount of memory, something around 260K, against the 320K of Blender 2.93.9. But slowly it grows and doesn't stop. Just moving the mouse around or navigating through the scene.

At some points, for any reason, the memory in 2.93.9 also rises, but then it goes back to normal, but not in 3.2.2. It only rises.
At this point, this is the difference in memory usage for both for that specific scene:

Tried to create a new scene to see if Blender releases the memory, but no result. When working on my projects, I need to restart Blender to get the memory back to normal. That happens several times a day, depending on the size of the project.

Now that I am finishing to explain, I see that the 2.93.9 memory usage raised a bit, it's on:
But if I open the window there, it goes back to normal, but not the 3.2.2.

To prove that, I just opened the 2.93.9 window and see what happened: it went back to the initial amount of memory. But the 3.2.2 only rises. Now, at the end of this report:

Exact steps for others to reproduce the error
Open blender in a default scene and see the memory consumption rise as you move the mouse around.

I tried to find similar reports to avoid duplicating them, but I did not find any similar ones.

PS: I've tried all versions of Blender since 3.0 I have here and the same happens to all of them.

**System Information** Operating system: Linux-5.13.0-44-generic-x86_64-with-glibc2.31 64 Bits Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01 **Blender Version** Broken: version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: `bcfdb14560` Worked: version: 2.93.9, branch: master, commit date: 2022-04-19 14:25, hash: `31712ce77a` **Short description of error** I just open any version of Blender since 3.0 and just moving the mouse around makes the amount of memory used by Blender rise. It doesn't stop. It doesn't liberate the memory, ever. It just goes higher and higher, until the memory is full. At first, I thought it was something related to the projects and operations I was doing. I tried to reduce the undo steps and everything else that's advised to reduce memory consumption, and today I realized that simply moving the mouse around was already increasing the memory usage of Blender. I don't need to do any actions Now, I have two versions of Blender open, to compare 2.93.9 and 3.2.2. Both have the same scene: Susanne, a camera, and a point light. At first, Blender 3.2.2 started with a smaller amount of memory, something around 260K, against the 320K of Blender 2.93.9. But slowly it grows and doesn't stop. Just moving the mouse around or navigating through the scene. At some points, for any reason, the memory in 2.93.9 also rises, but then it goes back to normal, but not in 3.2.2. It only rises. At this point, this is the difference in memory usage for both for that specific scene:![image.png](https://archive.blender.org/developer/F13406020/image.png) Tried to create a new scene to see if Blender releases the memory, but no result. When working on my projects, I need to restart Blender to get the memory back to normal. That happens several times a day, depending on the size of the project. Now that I am finishing to explain, I see that the 2.93.9 memory usage raised a bit, it's on: ![image.png](https://archive.blender.org/developer/F13406038/image.png) But if I open the window there, it goes back to normal, but not the 3.2.2. To prove that, I just opened the 2.93.9 window and see what happened: it went back to the initial amount of memory. But the 3.2.2 only rises. Now, at the end of this report: ![image.png](https://archive.blender.org/developer/F13406050/image.png) **Exact steps for others to reproduce the error** Open blender in a default scene and see the memory consumption rise as you move the mouse around. I tried to find similar reports to avoid duplicating them, but I did not find any similar ones. PS: I've tried all versions of Blender since 3.0 I have here and the same happens to all of them.

👀 1

Rodrigo Couto commented

2022-08-19 18:48:12 +02:00

Added subscriber: @Calandro

Rodrigo Couto commented

2022-08-19 22:06:42 +02:00

I kept both windows open. Did something in a project in Blender 3.2.2 and came back to the Susanne scene. Although some of the memory that was being used for the project was released, a huge amount is still unavailable. I did the same in Blender 2.93 to see what happens and when I went back to the Suzanne scene it started using even less memory than before.

I think that's a huge difference for the same scene in both versions.

I kept both windows open. Did something in a project in Blender 3.2.2 and came back to the Susanne scene. Although some of the memory that was being used for the project was released, a huge amount is still unavailable. I did the same in Blender 2.93 to see what happens and when I went back to the Suzanne scene it started using even less memory than before. ![image.png](https://archive.blender.org/developer/F13406449/image.png) I think that's a huge difference for the same scene in both versions.

Yegor commented

2022-08-21 19:05:25 +02:00

Added subscriber: @YegorSmirnov

Yegor commented

2022-08-21 19:05:25 +02:00

Can confirm. This is the greatest bug of all time! :)
Undo is disabled. 3.2.2, 3.3 versions affected. 2.93.10 works correctly.
2022-08-21_20-03-21.mp4

Can confirm. This is the greatest bug of all time! :) Undo is disabled. 3.2.2, 3.3 versions affected. 2.93.10 works correctly. [2022-08-21_20-03-21.mp4](https://archive.blender.org/developer/F13409624/2022-08-21_20-03-21.mp4)

Rodrigo Couto commented

2022-08-22 16:24:59 +02:00

In #100505#1406690, @YegorSmirnov wrote:
Can confirm. This is the greatest bug of all time! :)
Undo is disabled. 3.2.2, 3.3 versions affected. 2.93.10 works correctly.

Even stranger is that your memory consumption problem is even worse than mine, cause in my PC it doesn't grow so quickly. I'm impressed.

> In #100505#1406690, @YegorSmirnov wrote: > Can confirm. This is the greatest bug of all time! :) > Undo is disabled. 3.2.2, 3.3 versions affected. 2.93.10 works correctly. Even stranger is that your memory consumption problem is even worse than mine, cause in my PC it doesn't grow so quickly. I'm impressed.

Yegor commented

2022-08-22 22:39:50 +02:00

Ok, a clue to the problem might be in the 'old' videocards. I have 1080ti with latest drivers on linux Mint.
The problem is not presented on my another machine with 3070.

Ok, a clue to the problem might be in the 'old' videocards. I have 1080ti with latest drivers on linux Mint. The problem is not presented on my another machine with 3070.

Rodrigo Couto commented

2022-08-22 22:58:19 +02:00

Still feels like a problem to me as I have no way to upgrade my machine at this point to solve that. In the same way, it probably affects lots of other users, and even worse, some of them with even less RAM than me to deal with that.

JCS commented

2022-08-25 22:52:56 +02:00

Added subscriber: @dotted

JCS commented

2022-08-25 22:52:56 +02:00

I can confirm the same kind of problems with VSE for iMac 21" M1 (only a month old box). I have a simple template project of a background for 1080 video that has also a few animated stills. As soon as video is played, memory creeps up until it uses up all available memory requiring a forced quit. This issue is identical, though I had actually scraped all the other video and audio out of the project to use it as a template.

Therefore I do not think it's related necessarily to a video card.

I can offer a work around: save frequently and use a memory monitor. when it starts to top out, reload the project. It drops the memory right back to its initial footprint.

I can confirm the same kind of problems with VSE for iMac 21" M1 (only a month old box). I have a simple template project of a background for 1080 video that has also a few animated stills. As soon as video is played, memory creeps up until it uses up all available memory requiring a forced quit. This issue is identical, though I had actually scraped all the other video and audio out of the project to use it as a template. Therefore I do not think it's related necessarily to a video card. I can offer a work around: save frequently and use a memory monitor. when it starts to top out, reload the project. It drops the memory right back to its initial footprint.

Pratik Borhade commented

2022-08-26 08:32:14 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-08-26 08:32:14 +02:00

I'm not able to replicate this

In #100505#1406690, @YegorSmirnov wrote:
Can confirm. This is the greatest bug of all time! :)
Undo is disabled. 3.2.2, 3.3 versions affected. 2.93.10 works correctly.
F13409624

I don't think Undo functionality is responsible because memory consumption is rising before you finish the operation

Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78```

I'm not able to replicate this > In #100505#1406690, @YegorSmirnov wrote: > Can confirm. This is the greatest bug of all time! :) > Undo is disabled. 3.2.2, 3.3 versions affected. 2.93.10 works correctly. > [F13409624](https://archive.blender.org/developer/F13409624/2022-08-21_20-03-21.mp4) I don't think Undo functionality is responsible because memory consumption is rising before you finish the operation - - - ```**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78```

Rodrigo Couto commented

2022-08-30 01:35:16 +02:00

In #100505#1408533, @dotted wrote:
I can confirm the same kind of problems with VSE for iMac 21" M1 (only a month old box). I have a simple template project of a background for 1080 video that has also a few animated stills. As soon as video is played, memory creeps up until it uses up all available memory requiring a forced quit. This issue is identical, though I had actually scraped all the other video and audio out of the project to use it as a template.

Therefore I do not think it's related necessarily to a video card.

I can offer a work around: save frequently and use a memory monitor. when it starts to top out, reload the project. It drops the memory right back to its initial footprint.

That's exactly what I have been doing.

> In #100505#1408533, @dotted wrote: > I can confirm the same kind of problems with VSE for iMac 21" M1 (only a month old box). I have a simple template project of a background for 1080 video that has also a few animated stills. As soon as video is played, memory creeps up until it uses up all available memory requiring a forced quit. This issue is identical, though I had actually scraped all the other video and audio out of the project to use it as a template. > > Therefore I do not think it's related necessarily to a video card. > > I can offer a work around: save frequently and use a memory monitor. when it starts to top out, reload the project. It drops the memory right back to its initial footprint. That's exactly what I have been doing.

Omar Emara commented

2022-08-30 11:23:33 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-08-30 11:23:33 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Omar Emara commented

2022-08-30 11:23:33 +02:00

Can you also monitor VRAM usage and tell us what you see? Maybe the GPU is swapping to RAM causing the memory increase.

Yegor commented

2022-08-31 15:41:43 +02:00

In #100505#1410001, @OmarEmaraDev wrote:
Can you also monitor VRAM usage and tell us what you see? Maybe the GPU is swapping to RAM causing the memory increase.

On my system VRAM stays flat, while RAM rises

> In #100505#1410001, @OmarEmaraDev wrote: > Can you also monitor VRAM usage and tell us what you see? Maybe the GPU is swapping to RAM causing the memory increase. On my system VRAM stays flat, while RAM rises

Omar Emara commented

2022-08-31 15:42:29 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Rodrigo Couto commented

2022-09-02 03:23:59 +02:00

In #100505#1410001, @OmarEmaraDev wrote:
Can you also monitor VRAM usage and tell us what you see? Maybe the GPU is swapping to RAM causing the memory increase.

Same here. No significant changes in VRAM while RAM stays rising continuously.

> In #100505#1410001, @OmarEmaraDev wrote: > Can you also monitor VRAM usage and tell us what you see? Maybe the GPU is swapping to RAM causing the memory increase. Same here. No significant changes in VRAM while RAM stays rising continuously.

Yegor commented

2022-09-02 21:23:42 +02:00

Tried on windows (same hardware) - no issues. Seems like a linux version problem.

Rodrigo Couto commented

2022-09-03 00:40:34 +02:00

In #100505#1411789, @YegorSmirnov wrote:
Tried on windows (same hardware) - no issues. Seems like a linux version problem.

Oh, crap. 😒

> In #100505#1411789, @YegorSmirnov wrote: > Tried on windows (same hardware) - no issues. Seems like a linux version problem. Oh, crap. 😒

Rodrigo Couto commented

2022-09-11 18:50:23 +02:00

I'm glad to come here to announce that today I upgraded my Kubuntu to the 22.04 version and the problem just disappeared.

Yegor commented

2022-09-12 00:28:50 +02:00

Same here (almost). Upgraded my Mint to the current version. Memory consumption rises dragging an object back and forth, but really slow. Can't say it disappeared though.

Omar Emara commented

2022-09-12 09:30:07 +02:00

@YegorSmirnov I think a rise can be normal, but the question is, is it a memory leak? Does the memory get full after some time of working and never go down again until Blender becomes unresponsive?

Omar Emara commented

2022-09-12 09:30:18 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Yegor commented

2022-09-12 21:27:03 +02:00

Ok, updated all the software. Latest kernel and drivers. Still rises, but slow. Couldn't lower the consumption by rendering or creating a new file.
Here's a boring video x8 speed up. In 16 min in real time got to 1Gb. With the previous software setup it would take about 20Gb I guess.
0001-3819.mp4

Ok, updated all the software. Latest kernel and drivers. Still rises, but slow. Couldn't lower the consumption by rendering or creating a new file. Here's a boring video x8 speed up. In 16 min in real time got to 1Gb. With the previous software setup it would take about 20Gb I guess. [0001-3819.mp4](https://archive.blender.org/developer/F13485087/0001-3819.mp4)

Omar Emara commented

2022-09-13 09:14:12 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Rodrigo Couto commented

2022-09-13 10:42:01 +02:00

In #100505#1415940, @YegorSmirnov wrote:
Ok, updated all the software. Latest kernel and drivers. Still rises, but slow. Couldn't lower the consumption by rendering or creating a new file.

Yes, you are right. It's still happening at a much slower rate. I am happy that it got a bit better anyway, cause I believe a fix for that could take a long time to happen if someone thinks it is worth it.

> In #100505#1415940, @YegorSmirnov wrote: > Ok, updated all the software. Latest kernel and drivers. Still rises, but slow. Couldn't lower the consumption by rendering or creating a new file. Yes, you are right. It's still happening at a much slower rate. I am happy that it got a bit better anyway, cause I believe a fix for that could take a long time to happen if someone thinks it is worth it.

Damien Monteillard commented

2022-11-22 15:02:30 +01:00

Added subscriber: @lastrodamo

Damien Monteillard commented

2022-11-22 15:11:28 +01:00

I have the same problem. The memory grows all the time, even if I don't work on the opened project.

Here is my configuration:

System Information
Operating system: Linux-5.15.14-1-lts-x86_64-with-glibc2.33 64 Bits
Graphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.46

Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: b292cfe5a9
Worked: (newest version of Blender that worked as expected)

I have the same problem. The memory grows all the time, even if I don't work on the opened project. Here is my configuration: **System Information** Operating system: Linux-5.15.14-1-lts-x86_64-with-glibc2.33 64 Bits Graphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.46 **Blender Version** Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: `b292cfe5a9` Worked: (newest version of Blender that worked as expected)

Gabriel Wicke commented

2022-11-26 17:09:28 +01:00

Added subscriber: @gwicke

Gabriel Wicke commented

2022-11-27 19:00:48 +01:00

I suspect that the graphics setup might play into this. I was seeing significant leaking / RSS increase correlated especially with Blender rendering activity (active editing, rotating / zooming the viewport). However, I am not seeing this much after upgrading my graphics configuration to the newer modesetting Intel driver without driver-side buffering, and starting to use a compositor (compton) to provide frame buffering and vsync functionality. Repeatedly loading and browsing models of different complexity would previously reliably increase RSS over time, while now it looks more stable.

Common setup for both versions

Blender version: 3.3.1 (Debian unstable package)
Linux 6.0.0-4-amd64 (Debian unstable)
Intel 620 internal GPU (i915 driver)
i3 tiling window manager

Leaking graphics setup

xorg.conf with "AccelMethod" "sna" and "TearFree" "true"
** Causes triple buffering inside the older "intel" xorg driver. Avoids tearing, but significantly reduces performance.
no compositor

No or less leaking (so far)

Empty xorg conf - uses modesetting intel driver
** Better performance, but will produce a lot of tearing in firefox and generally scrolling use cases
Address tearing issue by using a compositor
** In my case: compton --vsync opengl --xrender-sync --backend glx --glx-swap-method 3 started from i3 config

I suspect that the graphics setup might play into this. I was seeing significant leaking / RSS increase correlated especially with Blender rendering activity (active editing, rotating / zooming the viewport). However, I am not seeing this much after upgrading my graphics configuration to the newer modesetting Intel driver without driver-side buffering, and starting to use a compositor (compton) to provide frame buffering and vsync functionality. Repeatedly loading and browsing models of different complexity would previously reliably increase RSS over time, while now it looks more stable. **Common setup for both versions** * Blender version: 3.3.1 (Debian unstable package) * Linux 6.0.0-4-amd64 (Debian unstable) * Intel 620 internal GPU (i915 driver) * i3 tiling window manager **Leaking graphics setup** * xorg.conf with "AccelMethod" "sna" and "TearFree" "true" ** Causes triple buffering inside the older "intel" xorg driver. Avoids tearing, but significantly reduces performance. * no compositor **No or less leaking (so far)** * Empty xorg conf - uses modesetting intel driver ** Better performance, but will produce a lot of tearing in firefox and generally scrolling use cases * Address tearing issue by using a compositor ** In my case: `compton --vsync opengl --xrender-sync --backend glx --glx-swap-method 3` started from i3 config

Damien Monteillard commented

2022-12-01 12:28:24 +01:00

I change my system with a fresh Gentoo with this config :

System Information
Operating system: Linux-5.15.75-gentoo-x86_64-Intel-R-_Core-TM-i7-3930K_CPU@_3.20GHz-with-glibc2.36 64 Bits
Graphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01

Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: b292cfe5a9

And At this moment, the memory does not rise anymore.
@gwicke My kernel (5.15.75) is more recent as @Calandro but I have the same GC driver. Maybe compilations with Gentoo is better in my case.

I change my system with a fresh Gentoo with this config : **System Information** Operating system: Linux-5.15.75-gentoo-x86_64-Intel-R-_Core-TM-_i7-3930K_CPU_@_3.20GHz-with-glibc2.36 64 Bits Graphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01 **Blender Version** Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: `b292cfe5a9` And At this moment, the memory does not rise anymore. @gwicke My kernel (5.15.75) is more recent as @Calandro but I have the same GC driver. Maybe compilations with Gentoo is better in my case.

Damien Monteillard commented

2022-12-01 20:33:04 +01:00

Another precision I do not use Optix on my blender 3.3.1 configuration.

Richard Antalik commented

2022-12-07 06:28:56 +01:00

Added subscriber: @iss

Richard Antalik commented

2022-12-07 06:28:56 +01:00

Just to check where this happens, can Linux users check if this happens when they run blender-softwaregl binary? Hope I got name right, I am on Windows...

Just to check where this happens, can Linux users check if this happens when they run `blender-softwaregl` binary? Hope I got name right, I am on Windows...

rantrave commented

2023-05-15 13:07:17 +02:00

I experience pretty same behavior on my installations (tried several versions from 3.0 to 3.5.1, from snap, ppa, built from source).

System: Ubuntu 22.04; 5.15.0-71-generic #78-Ubuntu SMP Tue Apr 18 09:00:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
GPU: Nvidia 2070 Super, Driver Version: 525.105.17
X.Org

Noted that memory leakage increases with mouse movement on any blender window (megabytes per second).

blender-softwaregl script produces same result.

2.93.10 works correctly.

I experience pretty same behavior on my installations (tried several versions from 3.0 to 3.5.1, from snap, ppa, built from source). ``` System: Ubuntu 22.04; 5.15.0-71-generic #78-Ubuntu SMP Tue Apr 18 09:00:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux GPU: Nvidia 2070 Super, Driver Version: 525.105.17 X.Org ``` Noted that memory leakage increases with mouse movement on any blender window (megabytes per second). `blender-softwaregl` script produces same result. 2.93.10 works correctly.

Damien Monteillard commented

2023-05-15 18:23:02 +02:00

@rantrave I think that this overgrown memory comes from a too old graphic card driver. Or not stable.
Look at this page https://packages.gentoo.org/packages/x11-drivers/nvidia-drivers

@rantrave I think that this overgrown memory comes from a too old graphic card driver. Or not stable. Look at this page https://packages.gentoo.org/packages/x11-drivers/nvidia-drivers

rantrave commented

2023-05-15 22:16:36 +02:00

@DamienMonteillard Just updated to 530 from official repository, nothing changed. The problem occurred before the latest driver release, changing driver to any nvidia-driver-*-open/nvidia-driver-* gives nothing too. Even with nouveau driver still the same problem presents.

Same behavior in wayland sessions.

@DamienMonteillard Just updated to 530 from official repository, nothing changed. The problem occurred before the latest driver release, changing driver to any `nvidia-driver-*-open`/`nvidia-driver-*` gives nothing too. Even with nouveau driver still the same problem presents. Same behavior in wayland sessions.

Campbell Barton commented

2023-11-30 09:53:57 +01:00

Does this issue occur under Wayland?

Damien Monteillard commented

2023-11-30 10:03:26 +01:00

Not in my case, I use X11

Iliya Katushenock commented

2024-04-07 22:38:49 +02:00

First of all, i don't know why this is a issue.
Blender can allocate new memory at any action and this can be not so obvious.
GPU buffers, threads things, mutex things, ... .
Next one:

Here's a boring video x8 speed up. In 16 min in real time got to 1Gb. With the previous software setup it would take about 20Gb I guess.
0001-3819.mp4

Even if you have 0 undo steps, blender still log your actions:

Which platforms can reproduce this issue? As i can see Linux, and not Wayland (?), is there any one on windows?

Maybe any one can check if this was fixed in latest versions?

First of all, i don't know why this is a issue. Blender can allocate new memory at any action and this can be not so obvious. GPU buffers, threads things, mutex things, ... . Next one: > Here's a boring video x8 speed up. In 16 min in real time got to 1Gb. With the previous software setup it would take about 20Gb I guess. [0001-3819.mp4](https://archive.blender.org/developer/F13485087/0001-3819.mp4) Even if you have 0 undo steps, blender still log your actions: ![image](/attachments/f8b66959-8623-4def-8834-ef72c4b4c6ce) Which platforms can reproduce this issue? As i can see Linux, and not Wayland (?), is there any one on windows? Maybe any one can check if this was fixed in latest versions?

image.png

69 KiB

rantrave commented

2024-04-08 14:07:58 +02:00

@mod_moder

First of all, i don't know why this is a issue.

In my case memory usage grows from mouse cursor movement on blender window. It grows till the crash with OOM.

As i can see Linux, and not Wayland

Tested both X11 and Wayland with different drivers, issue persists.

Maybe any one can check if this was fixed in latest versions?

Latest version of blender tested is Blender 4.1.0.

@mod_moder > First of all, i don't know why this is a issue. In my case memory usage grows from mouse cursor movement on blender window. It grows till the crash with OOM. > As i can see Linux, and not Wayland Tested both X11 and Wayland with different drivers, issue persists. > Maybe any one can check if this was fixed in latest versions? Latest version of blender tested is Blender 4.1.0.

👍 1

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Memory leak with no actions at all. #100505