Blender freezes when using Texture paint or Weight Paint #75452

New Issue

Kunal Das · 2020-04-06T19:56:50+02:00

Kunal Das commented

2020-04-06 19:56:50 +02:00

System Information
Operating system: Windows 10 Insider build19592
Graphics card: GTX 1660Ti Max Q 6GB
Processor: i7-9750H
RAM: 32GB DDR4-2666Mhz

Blender Version
Broken: version: 2.83 (sub 11), branch: arcpatch-D7019, commit date: 2020-04-07 09:45, hash: b2b0241aca
Worked: Never (2.79, 2.8+)

Short description of error
Blender freezes or stops responding when using Texture Paint or Weight Paint. Tried game ready and Studio drivers, still the same issue.
Moreover, RAM consumption spikes up to more than 20GB. This happens when the brush size is increased and starts painting.

Assigned GPU in Preferences>System>CUDA, but the GPU is been barely used.

Exact steps for others to reproduce the error
Blender.rar

**System Information** Operating system: Windows 10 Insider build19592 Graphics card: GTX 1660Ti Max Q 6GB Processor: i7-9750H RAM: 32GB DDR4-2666Mhz **Blender Version** Broken: version: 2.83 (sub 11), branch: arcpatch-[D7019](https://archive.blender.org/developer/D7019), commit date: 2020-04-07 09:45, hash: `b2b0241aca` Worked: Never (2.79, 2.8+) **Short description of error** Blender freezes or stops responding when using Texture Paint or Weight Paint. Tried game ready and Studio drivers, still the same issue. Moreover, RAM consumption spikes up to more than 20GB. This happens when the brush size is increased and starts painting. Assigned GPU in Preferences>System>CUDA, but the GPU is been barely used. **Exact steps for others to reproduce the error** [Blender.rar](https://archive.blender.org/developer/F8453112/Blender.rar)

Kunal Das commented

2020-04-06 19:56:50 +02:00

Added subscriber: @Gigakb

surya kiran reddy commented

2020-04-06 20:57:24 +02:00

Added subscriber: @DirSurya

Robert Guetzkow was assigned by Kunal Das

2020-04-07 04:55:43 +02:00

Ankit Meel commented

2020-04-07 09:18:55 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2020-04-07 09:18:55 +02:00

#75284 (Huge memory usage when trying to paint on UVs far ouside the 0-1 range)

Ankit Meel commented

2020-04-07 11:27:57 +02:00

Closed as duplicate of #75284

Ankit Meel closed this issue

2020-04-07 11:27:57 +02:00

Robert Guetzkow was unassigned by Ankit Meel

2020-04-07 11:29:10 +02:00

Ankit Meel commented

2020-04-07 11:29:10 +02:00

Added subscriber: @rjg

Ankit Meel commented

2020-04-07 11:29:10 +02:00

was it discussed with Robert already ?

Robert Guetzkow commented

2020-04-07 11:36:21 +02:00

@ankitm No it wasn't.

@Gigakb Please don't assign the task yourself. This will be done by the development coordinators, module owners and developers.

@ankitm No it wasn't. @Gigakb Please don't assign the task yourself. This will be done by the development coordinators, module owners and developers.

Robert Guetzkow commented

2020-04-07 11:42:03 +02:00

Changed status from 'Duplicate' to: 'Needs Triage'

Robert Guetzkow reopened this issue

2020-04-07 11:42:03 +02:00

Kunal Das commented

2020-04-07 13:12:58 +02:00

@rjg sorry my bad! I thought the poster needs to assign things.

I apologize...

@rjg sorry my bad! I thought the poster needs to assign things. I apologize...

Richard Antalik commented

2020-04-07 15:43:29 +02:00

Added subscriber: @iss

Richard Antalik commented

2020-04-07 15:43:29 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Richard Antalik commented

2020-04-07 15:43:29 +02:00

Can confirm this.

Also this doesn't look like the same problem as #75284 by havin quick look at code paths and performance profiler.

Can confirm this. Also this doesn't look like the same problem as #75284 by havin quick look at code paths and performance profiler.

Kunal Das commented

2020-04-11 05:35:36 +02:00

any update?

Jeroen Bakker commented

2020-05-19 13:29:55 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2020-05-19 13:29:55 +02:00

Weight and projection painting isn't optimized for dense meshes. Marking this as a known issue.

ManiaC commented

2020-07-10 21:28:28 +02:00

Added subscriber: @maniacalipsis

ManiaC commented

2020-07-10 21:28:28 +02:00

A little more info around this problem:
Finally I had bought 8GB more RAM (16GB total now) and started to paint on 16Kx8K texture. It was successfully loaded and after this the memory usage was ok. But only the first time, until I started to paint. And the more I painted, the blender allocated more and more gigabytes until It ate'em all. I thought that it's a problem of "Undo" and setted "Undo memory limit" to 2GB, but nothing had change. Also, tracking a memory usage while painting, I noticed that a new portion of memory is allocated after each swap of the brush colors.
Then I made a test:

Make and unwrap any model, e.g. cube, and assign a material with an image texture. (4K and 8K was tested)
Switch to Texture paint mode and paint over it, quickly swapping brush colors.

Results are following:

(new 8K texture)

(I started to paint, swapping colors after each stroke)

(And nothing freed after some wait, but continued go on)

(Finally, I started to paint some time without color swapping, and - O-miracle - a lot of memory had freed in a short time. But when I started to swap again - all comes back)

(Settings)

By the way: when I tried the same with 4K texture, the memory consumption looks similar by the principle but not so impressive by variation of amount.

p.s. Painting freezes while allocating each portion of memory (that is obviously).

Hope this may help to improve performanse of this tool/module/code at all.

p.p.s.: Don;t know how to painting undo is realized, but I think that it may be so:

locate a rectangular region where are the pixels will be affected by pending painting operation
copy this region and its coords into the undo stack (only array of pixel colors not all the X,Y,Z,U and W)

apply current painting op. (actually change pixels)

And to make the undo - just copy last stored rect back to the image.
Thus expenses will be proportional to size of the area, modified by single operation. I know, this will be expensive for the huge and wide strokes, but finally it's rateably and predictable.
(Also m.b. some improvement is possible, for example, divide large rect on several smaller ones and reject that ones, which wasn't actually affected. E.g. if a large thin circle was painted).

A little more info around this problem: Finally I had bought 8GB more RAM (16GB total now) and started to paint on 16Kx8K texture. It was successfully loaded and after this the memory usage was ok. But only the first time, until I started to paint. And the more I painted, the blender allocated more and more gigabytes until It ate'em all. I thought that it's a problem of "Undo" and setted "Undo memory limit" to 2GB, but nothing had change. Also, tracking a memory usage while painting, I noticed that a new portion of memory is allocated after each swap of the brush colors. Then I made a test: - Make and unwrap any model, e.g. cube, and assign a material with an image texture. (4K and 8K was tested) - Switch to Texture paint mode and paint over it, quickly swapping brush colors. Results are following: ![Screenshot_20200710_205039.jpg](https://archive.blender.org/developer/F8684428/Screenshot_20200710_205039.jpg) (new 8K texture) ![Screenshot_20200710_205154.jpg](https://archive.blender.org/developer/F8684431/Screenshot_20200710_205154.jpg) (I started to paint, swapping colors after each stroke) ![Screenshot_20200710_205306.jpg](https://archive.blender.org/developer/F8684437/Screenshot_20200710_205306.jpg) (And nothing freed after some wait, but continued go on) ![Screenshot_20200710_210626.jpg](https://archive.blender.org/developer/F8684446/Screenshot_20200710_210626.jpg) (Finally, I started to paint some time without color swapping, and - O-miracle - a lot of memory had freed in a short time. But when I started to swap again - all comes back) ![Screenshot_20200710_205351.jpg](https://archive.blender.org/developer/F8684466/Screenshot_20200710_205351.jpg) (Settings) By the way: when I tried the same with 4K texture, the memory consumption looks similar by the principle but not so impressive by variation of amount. ![Screenshot_20200710_204936.jpg](https://archive.blender.org/developer/F8684490/Screenshot_20200710_204936.jpg) p.s. Painting freezes while allocating each portion of memory (that is obviously). Hope this may help to improve performanse of this tool/module/code at all. p.p.s.: Don;t know how to painting undo is realized, but I think that it may be so: - locate a rectangular region where are the pixels will be affected by pending painting operation - copy this region and its coords into the undo stack (only array of pixel colors not all the X,Y,Z,U and W) # apply current painting op. (actually change pixels) And to make the undo - just copy last stored rect back to the image. Thus expenses will be proportional to size of the area, modified by single operation. I know, this will be expensive for the huge and wide strokes, but finally it's rateably and predictable. (Also m.b. some improvement is possible, for example, divide large rect on several smaller ones and reject that ones, which wasn't actually affected. E.g. if a large thin circle was painted).

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender freezes when using Texture paint or Weight Paint #75452

apply current painting op. (actually change pixels)