And the gimp process itself doesn't do that? Are the two processes indicated as belonging to the gimp process while they are running? Does this happen with the build from gimp.org?

(In reply to Michael Schumacher from comment #1)
> And the gimp process itself doesn't do that? 

Gimp itself behaved normally when i got that bug. 

> Are the two processes indicated as belonging to the gimp process while they are running? 

Gimp activates python-fu or script-fu whenever you start to invoke plugins. They stand in you dock until you quit Gimp. Dont know the relations of Gimp with plugins, but i guess that Python scripts are less bound to Gimp.

Does this happen with the build from gimp.org?

both builds launch plugins as processes aside Gimp, and if one of these plugin processes rests open or stuck, my system refuses to shut down nicely. However, when quitting Gimp, also its processes should quit-dont know if my Os tries to quit Gimps processes before Gimp itself.

Can you provide a screenshot of your system's task manager, preferably with a tree view that show the processes' relationship to each other? If any of the default ones fail to offer that, then htop seems to be a recommended alternative.

We know we need to do something about these "background" processes that
are not really background processed. They should not appear in the
dock either.

Unfortunately we have around zero OS X developers...

Created attachment 308081 [details]
Gimp Plugin processes

attached:
open files and ports (3)
processes hierarchy  (1)

Hm... is this with the build from gimp.org? I wonder why some of the files and ports referenced there include "de.lisanet.gimp".

Is this the same as bug 710523?

(In reply to Michael Schumacher from comment #7)
> Is this the same as bug 710523?

probably, if the reporter used plugins. Else rather not.

You shouldn't have to use anything, Script-Fu is always run.

Or do you only experience this problem if you have run another plug-in? Does python stay around even when all python-based plug-ins have finished?

(In reply to Michael Schumacher from comment #9)
> You shouldn't have to use anything, Script-Fu is always run.
> 
> Or do you only experience this problem if you have run another plug-in? Does
> python stay around even when all python-based plug-ins have finished?

usually Gimp starts without any additional processes. 
Whenever i use Scripts, be it Script-fu or Python-fu, two processes appear in the dock, at least on Mac

i forgot: yes, both processes pythonfu and scriptfu stay open even when the scripts has finished their tasks/closed the dialogs.

(In reply to Michael Natterer from comment #4)
> We know we need to do something about these "background" processes that
> are not really background processed. They should not appear in the
> dock either.
> 
> Unfortunately we have around zero OS X developers...

A process like "python-fu" runs as standalone process and seems to open its own connection to the window server. IIRC, because of this it shows up in the dock.

The only background process that is always active is script-fu, which is the same behavior as on Linux.

I haven't tested the shut down procedure yet, too many tabs open atm :)

Created attachment 313698 [details]
shutdown scenario

i guess its better to show the progress of plugins (progress bar and progress info) in the status bar of Gimp to avoid that plugin processes invoke background processes which can hang and hinder a shutdown of the Os itself
so, the dialog would pop up just to get the use input and not for the execution of commands itself.

Kris, any news on the shutdown testing?

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/714.