Gradual selection performance degradation (potential memory leak issue) #95715

New Issue

Nathan R · 2022-02-12T00:16:30+01:00

Nathan R commented

2022-02-12 00:16:30 +01:00

System Information
Operating system: Windows-10-10.0.19042-SP0 64 Bits
Graphics card: Intel(R) HD Graphics 530 Intel 4.5.0 - Build 27.20.100.9168

Blender Version
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-02-09 23:56, hash: 2887df119c
Worked: Blender v2.90.1

Short description of error
Gradual performance degradation when using Geometry Nodes (also occurs in any other node editor). After 5 or so minutes, Blender begins to slow down (operations such as selection--and box selection--start to have a large delay, but only in object mode). Have noticed that moving nodes (pressing G key and moving cursor) leads to a large increase in Blender's memory usage (culminates at around 3,000 MB - 3,100 MB of RAM for a very simple scene containing only a basic cube). Moving the nodes usually increases blender's memory usage by 10 MB per every couple of seconds.

Exact steps for others to reproduce the error

Open geometry node editor / shader editor
Begin to drag nodes around and notice gradual increase in memory usage
After about 5 minutes of dragging, selection in object mode should be noticeably slower than just opening blender.

**System Information** Operating system: Windows-10-10.0.19042-SP0 64 Bits Graphics card: Intel(R) HD Graphics 530 Intel 4.5.0 - Build 27.20.100.9168 **Blender Version** Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-02-09 23:56, hash: `2887df119c` Worked: Blender v2.90.1 **Short description of error** Gradual performance degradation when using Geometry Nodes (also occurs in any other node editor). After 5 or so minutes, Blender begins to slow down (operations such as selection--and box selection--start to have a large delay, but only in object mode). Have noticed that moving nodes (pressing G key and moving cursor) leads to a large increase in Blender's memory usage (culminates at around 3,000 MB - 3,100 MB of RAM for a very simple scene containing only a basic cube). Moving the nodes usually increases blender's memory usage by 10 MB per every couple of seconds. **Exact steps for others to reproduce the error** 1. Open geometry node editor / shader editor 2. Begin to drag nodes around and notice gradual increase in memory usage 3. After about 5 minutes of dragging, selection in object mode should be noticeably slower than just opening blender.

Nathan R commented

2022-02-12 00:16:30 +01:00

Added subscriber: @Mosrod

Pratik Borhade commented

2022-02-12 07:10:14 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-02-12 07:10:14 +01:00

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

Pratik Borhade commented

2022-02-12 07:10:14 +01:00

Hi, thanks for the report. I don't see any difference on comparing performance of 2.83.17 and 3.2.0

Worked: Blender v2.90.1

You mean it's a regression? Have you found this issue on recent release versions (2.93, 3.0.0)?
Generally reports on performance are not considered as a bug (unless its regression)

To improve performance, consider using less complex geometry, simpler shaders and smaller textures.```
Can you reproduce  with factory startup? {nav File > Defaults > Load Factory Settings}

Hi, thanks for the report. I don't see any difference on comparing performance of 2.83.17 and 3.2.0 > Worked: Blender v2.90.1 You mean it's a regression? Have you found this issue on recent release versions (2.93, 3.0.0)? Generally reports on performance are not considered as a bug (unless its regression) ```While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports. To improve performance, consider using less complex geometry, simpler shaders and smaller textures.``` Can you reproduce with factory startup? {nav File > Defaults > Load Factory Settings}

Nathan R commented

2022-02-14 22:54:03 +01:00

Hi Pratik,
Yes, the performance issue is a regression (works perfectly/quickly right after starting Blender--this includes after loading complex files), but after a couple of minutes, Blender slows down. In other words, this makes performance a function of time elapsed/time editing versus a function of geometry complexity (have been able to load fairly complex files with very fast selection times).

I have been able to reproduce this with factory settings on recent release versions (2.93, 3.0.1, 3.1.0, 3.2.0) with the default cube--at first, Blender selection is quick, but then, it gradually slows down.

Hi Pratik, Yes, the performance issue is a regression (works perfectly/quickly right after starting Blender--this includes after loading complex files), but after a couple of minutes, Blender slows down. In other words, this makes performance a function of time elapsed/time editing versus a function of geometry complexity (have been able to load fairly complex files with very fast selection times). I have been able to reproduce this with factory settings on recent release versions (2.93, 3.0.1, 3.1.0, 3.2.0) with the default cube--at first, Blender selection is quick, but then, it gradually slows down.

Nathan R commented

2022-02-14 22:56:45 +01:00

Two videos demonstrating performance degradation (note: it does become slower than showcased in the first video):

After ~5 minutes:
HotpinkSoft84.mp4

Right after restart:
FullOrangered88.mp4

Two videos demonstrating performance degradation (note: it does become slower than showcased in the first video): After ~5 minutes: [HotpinkSoft84.mp4](https://archive.blender.org/developer/F12867443/HotpinkSoft84.mp4) Right after restart: [FullOrangered88.mp4](https://archive.blender.org/developer/F12867444/FullOrangered88.mp4)

Pratik Borhade commented

2022-02-15 07:48:58 +01:00

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

Richard Antalik commented

2022-02-15 17:00:31 +01:00

Added subscriber: @iss

Richard Antalik commented

2022-02-15 17:00:31 +01:00

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

Richard Antalik commented

2022-02-15 17:00:31 +01:00

Download mesa3d-21.3.5-release-msvc.7z from github.com/pal1000/mesa-dist-win/releases/tag/21.3.5, extract files opengl32.dll, libglapi.dll and libgallium_wgl.dll to folder next to blender.exe. This will enable opengl emulation, which will be slow, but it should otherwise workwithout issues.

Can you check if memory leak happens after you copy these files?

Quite likely duplicate of #86778

Download mesa3d-21.3.5-release-msvc.7z from github.com/pal1000/mesa-dist-win/releases/tag/21.3.5, extract files opengl32.dll, libglapi.dll and libgallium_wgl.dll to folder next to blender.exe. This will enable opengl emulation, which will be slow, but it should otherwise workwithout issues. Can you check if memory leak happens after you copy these files? Quite likely duplicate of #86778

Nathan R commented

2022-02-19 00:45:41 +01:00

Hi Richard,
After looking through #86778, I was able to follow the steps and solve the issue (outdated graphics drivers).

Thank you so much for your quick support,
Nathan

Hi Richard, After looking through #86778, I was able to follow the steps and solve the issue (outdated graphics drivers). Thank you so much for your quick support, Nathan

Richard Antalik commented

2022-02-20 17:12:22 +01:00

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

Richard Antalik closed this issue

2022-02-20 17:12:22 +01:00

Richard Antalik commented

2022-02-20 17:12:22 +01:00

Thanks for update, will close then

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

Gradual selection performance degradation (potential memory leak issue) #95715