Memory leak in image_paint operator #75172

Closed
opened 2020-03-28 22:40:40 +01:00 by Joshua Knauber · 6 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 25.20.100.6472

Blender Version
Broken: version: 2.83 (sub 11), branch: master, commit date: 2020-03-28 14:08, hash: a882debee0

Short description of error
There seems to be some sort of a memory leak when using the image_paint operator.

Exact steps for others to reproduce the error

  • Open a new blend file and run this script:
    painting_modal.py

  • Go to texture painting mode and add an image texture to the texture painting slot.

  • Run the Paint Modal operator from the operator search

  • Paint on the object with Shift + Leftclick
    The memory usage in the bottom right corner goes up very quickly the more you paint.
    I asked about this issue on the blender stackexchange but didn't get any feedback that this is an issue with my code. Therefore I'm assuming that this is a bug.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 25.20.100.6472 **Blender Version** Broken: version: 2.83 (sub 11), branch: master, commit date: 2020-03-28 14:08, hash: `a882debee0` **Short description of error** There seems to be some sort of a memory leak when using the image_paint operator. **Exact steps for others to reproduce the error** - Open a new blend file and run this script: [painting_modal.py](https://archive.blender.org/developer/F8433562/painting_modal.py) - Go to texture painting mode and add an image texture to the texture painting slot. - Run the Paint Modal operator from the operator search - Paint on the object with Shift + Leftclick The memory usage in the bottom right corner goes up very quickly the more you paint. I asked about this issue on the blender stackexchange but didn't get any feedback that this is an issue with my code. Therefore I'm assuming that this is a bug.
Author

Added subscriber: @JoshuaKnauber

Added subscriber: @JoshuaKnauber

Added subscriber: @ideasman42

Added subscriber: @ideasman42

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

Changed status from 'Needs Triage' to: 'Archived'
Campbell Barton self-assigned this 2020-03-29 08:07:44 +02:00

Every separate call to bpy.ops.paint.image_paint adds a new undo step.
The cause of higher memory is every mouse movement is a separate undo step.

Even though this could be supported, it's not an error in the code.

Closing.

Every separate call to `bpy.ops.paint.image_paint` adds a new undo step. The cause of higher memory is every mouse movement is a separate undo step. Even though this could be supported, it's not an error in the code. Closing.
Author

This comment was removed by @JoshuaKnauber

*This comment was removed by @JoshuaKnauber*
Author

In #75172#899672, @ideasman42 wrote:
Every separate call to bpy.ops.paint.image_paint adds a new undo step.
The cause of higher memory is every mouse movement is a separate undo step.

I assumed something like this was the problem but then I'm not sure I understand why calling the operator with the undo parameter set to False like this:
bpy.ops.paint.image_paint(context.copy(),"EXEC_DEFAULT",False)
has the same effect

> In #75172#899672, @ideasman42 wrote: > Every separate call to `bpy.ops.paint.image_paint` adds a new undo step. > The cause of higher memory is every mouse movement is a separate undo step. I assumed something like this was the problem but then I'm not sure I understand why calling the operator with the undo parameter set to False like this: ```bpy.ops.paint.image_paint(context.copy(),"EXEC_DEFAULT",False)``` has the same effect
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#75172
No description provided.