Memory leakage after copy/paste and close an image

Bug #1074851 reported by grofaty on 2012-11-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Pinta-1.5-preview-20121103 on Windows XP:
1. New image 2000 x 2000.
2. Paint Bucket and click on canvas to fill it.
3. CTRL+A to mark whole canvas.
4. CTRL+C to copy an image.
5. Open Windows Task Manager to monitor memory consumption. Remember memory consumption.
6. CTRL+V to paste an image.
7. Repeat previous step for 20 times (I know stupid thing to paste the same image again and again).
8. CTLR+W to close an image.
9. Now when image is closed I expect to free up a memory to the level of step 5. But memory is not released in the same amount. So there is probably some memory leakage.

See attached image.

grofaty (grofaty) wrote :
Cameron White (cameronwhite91) wrote :

This only seems to happen in certain situations - for example, doing several paintbrush actions on a 10000x10000 image doesn't result in this issue.

Changed in pinta:
importance: Undecided → Medium
milestone: none → 1.5
status: New → Confirmed
Cameron White (cameronwhite91) wrote :

I fixed some of the memory usage issues:

There is still some unreleased memory that I haven't been able to track down yet, but the memory usage is significantly better now.

Changed in pinta:
assignee: nobody → Cameron White (cameronwhite91)
status: Confirmed → In Progress
grofaty (grofaty) wrote :

Retested using master on Windows XP and it looks better (comparing to #1). So it looks some memory is getting free after this actions.

grofaty (grofaty) wrote :

I suggest to postpone this bug after 1.5. It's going to effect only computer with low spec and it will effect them less, because some memory leakage was fixed.

Cameron White (cameronwhite91) wrote :

Yeah, I'm ok with that, since a lot of the memory usage has been fixed.

I'm unassigning myself, in case anyone else feels like working on this.

Changed in pinta:
assignee: Cameron White (cameronwhite91) → nobody
milestone: 1.5 → 1.6
Changed in pinta:
milestone: 1.6 → 1.7
status: In Progress → Triaged
Cameron White (cameronwhite91) wrote :

I don't think this is a release blocker for v1.7.

Changed in pinta:
milestone: 1.7 → none
grofaty (grofaty) wrote :

I agree we can postpone this problem.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers