David, using GIMP 2.10.18 I have problems with my pink wrapper! Same build of the plugin runs on 2.10.14 (build from Gimp.org) smooth. Still with 2.10.18 (MacPorts build, build from gimp.org still not ready) “Pink Operator” hangs and stops with time out. “Pink Operator binary” works fluently!
Is there a change in the GIMP plugin interface from …14 to …18? Are perhaps images stored or used with 16bit per pixel? Trying “Pink Operator” → “Wshedtopo” and with several other entries I get a corrupted preview or time out!
With the 2.10.14 version results are coming in a second, in 2.10.18 only the binary processing pink routines are working. Thats the reason to think about pixel representation!
It seems to work for me…
There have been a slight change in the way the command parallel works, in case an error occurs in one of the threads. Now, an abort signal is sent to all running threads to make them stop asap.
Command apply_timeout uses precisely this mechanism.
Hmm, a new build and update don’t show any difference with Gimp 2.10.18
Still now Gimp 2.10.14 is equal to 2.10.18. So to say an adjustment to the worse!
I have found some problems: Gimp …18 seems to be more (or less) aware on pixel representation! I think if the plugin returns an image with different pixel size to gimp it will make sometimes trouble.
In my case, sometimes output file.pnk resulted in a format with float numbers or long integer which were either not well accepted by pink binaries or by gimp. A late regression of output of pnk file format with type option. I will further look into that and will try to correct that. At least these things are quite new since the base functions were tested and did not show such behavior !
I can confirm the timeout in GIMP 2.10.14 using the latest plugin. When I select pink operator from the menu, I see two flashes of consoles opening and closing followed by the timeout notice in preview window.
@afre and @Reptorian, do you have the PINK binaries installed so that the filter has a chance to succeed ? Otherwise, I’m not surprised you get a preview timeout!
@KaRo, anyway, we still have to figure out what is going on with the timeout issue.
Could you make some test with command apply_timeout, from the command line and from the plug-in to see if this is working as expected?
The todays latest build of the plugin, update, corrected Pink Operator, shows again differences in Gimp 2.10.18 and 2.10.14.
Under …14 “Pink Test operator Bianca” works, not under …18 (immediate time out)! Up to now, I have not found the breaking point in fx_karo_pink_bianca!
David, seemingly the timeout message appears also in cases where an x call breaks without the necessary time used!
Still I have not fully understood the problem with temporarily used long integer or float images inside the plugin! Just with “Bianca” there is a last x call to label (from pink) resulting in a P8 pnk file (integer 32bit). Could it be that something is with the dynamic use of memory space?
In “Pink Operator” I have rounded the images for input to pink routines to prepare byte files. Most of the binaries used accept only 8bit pixels. Again still it surprises me that it works with one build and not in another!
The examples with the ‘fatal error’ are interesting.
I cannot reproduce this on my machine (i.e. it works here).
Could you try compiling gmic with make debug, with the address sanitizer enabled ?
