Blender 2.81 Sculpting on ubuntu 18.04 fills memory gradually #71866

New Issue

Ako · 2019-11-24T19:38:51+01:00

Ako commented

2019-11-24 19:38:51 +01:00

System Information
Operating system: Ubuntu 18.04
Graphics card: GEForce 940 MX

Blender Version
Broken: (example: 2.81, Linux, Glibc217,)

Blender 2.81 fills memory when i'm Sculpting gradually, and does not free it on exit. I have to restart my system to free the memory.( in this latest build it frees memory a little but not completely). it works fine in 2.80 and previous versions but in all 2.81 versions I tried I had this problem, I was hoping in the final build, blender team solve this problem but it still exists there and with all refinements in 2.81 for sculpting I can't use it. BTW I'm using Dyntopo for sculpting. When I look at "monitor" app in Ubuntu it shows that "Xorg" fills memory.

**System Information** Operating system: Ubuntu 18.04 Graphics card: GEForce 940 MX **Blender Version** Broken: (example: 2.81, Linux, Glibc217,) Blender 2.81 fills memory when i'm Sculpting gradually, and does not free it on exit. I have to restart my system to free the memory.( in this latest build it frees memory a little but not completely). it works fine in 2.80 and previous versions but in all 2.81 versions I tried I had this problem, I was hoping in the final build, blender team solve this problem but it still exists there and with all refinements in 2.81 for sculpting I can't use it. BTW I'm using Dyntopo for sculpting. When I look at "monitor" app in Ubuntu it shows that "Xorg" fills memory.

Ako commented

2019-11-24 19:38:51 +01:00

Added subscriber: @Akov

Pablo Dobarro was assigned by Bartosz Moniewski

2019-11-25 01:38:57 +01:00

YAFU commented

2019-11-25 02:26:58 +01:00

Added subscriber: @YAFU

YAFU commented

2019-11-25 02:26:58 +01:00

Please give information about the driver you use. For example you share here the result of each of the following lines from the terminal:

sudo lshw -c video

cat /proc/driver/nvidia/version

Please give information about the driver you use. For example you share here the result of each of the following lines from the terminal: ``` sudo lshw -c video ``` ``` cat /proc/driver/nvidia/version ```

Ako commented

2019-11-25 06:00:13 +01:00

hi, this is return of 'lshw' command:

  *-display                 
       description: VGA compatible controller
       product: HD Graphics 620
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 02
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:127 memory:ed000000-edffffff memory:c0000000-cfffffff ioport:f000(size=64) memory:c0000-dffff
  *-display
       description: 3D controller
       product: GM108M [GeForce 940MX]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a2
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:129 memory:ee000000-eeffffff memory:d0000000-dfffffff memory:e0000000-e1ffffff ioport:e000(size=128) memory:ef000000-ef07ffff

and my nvidia driver version:

NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 CDT 2019
GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)

hi, this is return of 'lshw' command: ``` *-display description: VGA compatible controller product: HD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:127 memory:ed000000-edffffff memory:c0000000-cfffffff ioport:f000(size=64) memory:c0000-dffff *-display description: 3D controller product: GM108M [GeForce 940MX] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:129 memory:ee000000-eeffffff memory:d0000000-dfffffff memory:e0000000-e1ffffff ioport:e000(size=128) memory:ef000000-ef07ffff ``` and my nvidia driver version: ``` NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ```

Maciej Jutrzenka commented

2019-11-26 00:03:56 +01:00

Added subscriber: @MaciejJutrzenka

Maciej Jutrzenka commented

2019-11-26 00:03:56 +01:00

can u upload file when your memory usage is for example at 10gb RAM? we could download it.. and test what is our ram usage. with such file..

Ako commented

2019-11-26 16:56:45 +01:00

its a big file with 184mb size, and I just have 8gb of RAM. can't upload it here.
Update: I tried many times, it's not the file, I mean just opening a file that I sculpted before doesn't fills RAM, it fills some parts of my RAM, but when I close that file, my RAM gets free again, but when I sculpt, 'Xorg' consumes RAM gradually until there it fills it, and when I close the file or even blender my RAM doesn't get free. it seems somehow a garbage collector doesn't work fine. also when I open a big file, it shows that blender consumed my RAM and not Xorg, but after some sculpting 'Xorg' consumes RAM too.
I hope I could explain the situation well.

its a big file with 184mb size, and I just have 8gb of RAM. can't upload it here. Update: I tried many times, it's not the file, I mean just opening a file that I sculpted before doesn't fills RAM, it fills some parts of my RAM, but when I close that file, my RAM gets free again, but when I sculpt, 'Xorg' consumes RAM gradually until there it fills it, and when I close the file or even blender my RAM doesn't get free. it seems somehow a garbage collector doesn't work fine. also when I open a big file, it shows that blender consumed my RAM and not Xorg, but after some sculpting 'Xorg' consumes RAM too. I hope I could explain the situation well.

Ako commented

2019-12-01 16:23:57 +01:00

any news from this?

Germano Cavalcante commented

2019-12-03 15:54:04 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-12-03 15:54:04 +01:00

Can you see if the same happens if you reduce the amount of undo steps?
Preferences -> System -> Undo Steps

Can you see if the same happens if you reduce the amount of undo steps? `Preferences -> System -> Undo Steps`

Ako commented

2019-12-03 16:32:16 +01:00

In #71866#823156, @mano-wii wrote:
Can you see if the same happens if you reduce the amount of undo steps?
Preferences -> System -> Undo Steps

Hi, I tested it, it was the default 32 undo steps, reduced it to 2, it somehow slowed rate of filling RAM, but it's still there.

> In #71866#823156, @mano-wii wrote: > Can you see if the same happens if you reduce the amount of undo steps? > `Preferences -> System -> Undo Steps` Hi, I tested it, it was the default 32 undo steps, reduced it to 2, it somehow slowed rate of filling RAM, but it's still there.

Germano Cavalcante commented

2019-12-03 16:39:33 +01:00

The same happens if you reduce to zero?
Could you describe the steps to reproduce the problem?

The same happens if you reduce to zero? Could you describe the steps to reproduce the problem?

Ako commented

2019-12-03 16:46:59 +01:00

Blender doesn't let me to reduce it to Zero, minimum is 2.
I don't know how to reduce the problem actually, but when I reduced undo steps to 2, the amount of RAM that Xorg fills, grows more slowly than when undo steps is 32.

Blender doesn't let me to reduce it to Zero, minimum is 2. I don't know how to reduce the problem actually, but when I reduced undo steps to 2, the amount of RAM that Xorg fills, grows more slowly than when undo steps is 32.

Ako commented

2019-12-03 16:50:26 +01:00

In #71866#823190, @Akov wrote:
Blender doesn't let me to reduce it to Zero, minimum is 2.
I don't know how to reduce the problem actually, but when I reduced undo steps to 2, the amount of RAM that Xorg fills, grows more slowly than when undo steps is 32.

sorry, I misunderstood your comment, read reproduce to reduce.
I just open blender and sculpt and use Dyntopo, nothing more, nothing less.

> In #71866#823190, @Akov wrote: > Blender doesn't let me to reduce it to Zero, minimum is 2. > I don't know how to reduce the problem actually, but when I reduced undo steps to 2, the amount of RAM that Xorg fills, grows more slowly than when undo steps is 32. sorry, I misunderstood your comment, read reproduce to reduce. I just open blender and sculpt and use Dyntopo, nothing more, nothing less.

Ako commented

2019-12-13 13:29:45 +01:00

I changed my DE to Gnome and the problem is solved, it seems Xserver has some problems with blender!

Germano Cavalcante commented

2019-12-13 13:56:52 +01:00

Changed status from 'Open' to: 'Archived'

Germano Cavalcante closed this issue

2019-12-13 13:56:52 +01:00

Germano Cavalcante commented

2019-12-13 13:56:52 +01:00

In this case it is even harder to know what is going on.
If necessary, I think it is better to make another report describing in detail how to reproduce the problem.
Closing this.

In this case it is even harder to know what is going on. If necessary, I think it is better to make another report describing in detail how to reproduce the problem. Closing this.

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

Blender 2.81 Sculpting on ubuntu 18.04 fills memory gradually #71866