Re: [Gimp-developer] Simultaneous Multiprocessing and Multithreading in GIMP
- From: Ahmad Nouralizadeh <ahmad mlists gmail com>
- To: Liam R E Quin <liam holoweb net>
- Cc: gimp-developer-list gnome org
- Subject: Re: [Gimp-developer] Simultaneous Multiprocessing and Multithreading in GIMP
- Date: Wed, 30 Oct 2019 05:48:49 +0330
Hi Liam,
Thanks for the answer.
On Sat, 26 Oct 2019 at 16:25, Liam R E Quin <liam holoweb net> wrote:
On Sat, 2019-10-26 at 15:30 +0330, Ahmad Nouralizadeh via gimp-
developer-list wrote:
AFAIK, using fork
and multithreading is not recommended (e.g., look at the second
answer here, Is it safe to fork from within a thread?
It's “not recommended” in the same way that using a knife to cut your
meat is not recommended: you could hurt yourself.
As you can see from that stackoverflow question, there can be problems
if you don't call exec() right away in the child process after a
fork(). Which GIMP does, avoiding the problems.
This is why GIMP does not deadlock when you run a plugin.
slave liam (ankh)
--
Liam Quin - web slave for https://www.fromoldbooks.org/
with fabulous vintage art and fascinating texts to read.
Click here to have the slave beaten.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]