After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 468658 - Contiguous Selection Tool: hangs gimp and vista
Contiguous Selection Tool: hangs gimp and vista
Status: RESOLVED DUPLICATE of bug 479875
Product: GIMP
Classification: Other
Component: Tools
2.2.x
Other Windows
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-08-20 20:57 UTC by James Monteath
Modified: 2008-01-15 13:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
image example (278.94 KB, application/octet-stream)
2007-08-24 15:36 UTC, James Monteath
Details

Description James Monteath 2007-08-20 20:57:19 UTC
The selection tool will select properly, however will slow the system down badly.  This only happens on windows vista not Linux.


Steps to reproduce:

1- Use the Contiguous tool
2- Have only 1 layer selected
3- Select the a thin portion of the image then reverse the selection (ctrl+i)
or
4- Shift select the closed sections of the image so that you have more than 10-15 regions selected.


Actual Results:

This will have the selection start to blink slowly, and will get slower response from Gimp when moving the image window around or even anything on Windows after this point.  The pattern seems to be an increase in number of selected regions.  No matter how i have them selected. The problem occurs when there are more than 10-15 selected regions.

If I am lucky I can close just window with the image, if not, I have to kill gimp using the Task Manager or even worse hard reboot the laptop.

While this is happening the process takes 100% of the CPU.

Expected results:

Work as on Linux, it should not slow down to a crawl and have to kill gimp or even hard reboot my vista machine.


Other info:

GTK+ 2.10.13 runtime
2GB memory
Comment 1 Michael Schumacher 2007-08-23 12:16:20 UTC
How much memory may GIMP use?
Comment 2 James Monteath 2007-08-24 15:36:21 UTC
Created attachment 94272 [details]
image example
Comment 3 James Monteath 2007-08-24 15:37:23 UTC
(In reply to comment #2)
> Created an attachment (id=94272) [edit]
> image example
> 


It uses 49MB and 60MB peak.  The memory does not increase when this happens.

The problem is when you move the image window when you have selected items, and really slows down the system.

I will attach an example image.

Comment 4 Raphaël Quinet 2007-08-24 16:57:42 UTC
(In reply to comment #3)
> It uses 49MB and 60MB peak.  The memory does not increase when this happens.

I guess that what Michael wanted to know in comment #1 was how much memory you allow GIMP to use, in other words: how did you set the "Tile cache size" in File->Preferences->Environment ?  If you have 2 GB RAM, then you should probably set this parameter to 1500 MB or more.  I doubt that it is the source of this problem, but configuring the tile cache correctly cannot hurt.
Comment 5 James Monteath 2007-08-24 22:16:09 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > It uses 49MB and 60MB peak.  The memory does not increase when this happens.
> 
> I guess that what Michael wanted to know in comment #1 was how much memory you
> allow GIMP to use, in other words: how did you set the "Tile cache size" in
> File->Preferences->Environment ?  If you have 2 GB RAM, then you should
> probably set this parameter to 1500 MB or more.  I doubt that it is the source
> of this problem, but configuring the tile cache correctly cannot hurt.
> 

It is set the same as in Linux, which only windows has the problem.  This file is very small also.

It was set at 256, tried 512 still same problem.

Also notice that when this happens, the windows cursor cannot select items on the windows application bar where i need to access the task manager.

I have to ctrl-alt-delete to get to the task manager, so i can kill gimp.

Comment 6 Sven Neumann 2007-09-11 06:29:33 UTC
We have worked on improving this for 2.4. Please test a release candidate and report back.
Comment 7 Michael Schumacher 2007-12-06 09:33:37 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 479875 ***