pike issueshttps://git.lysator.liu.se/pikelang/pike/-/issues2009-04-16T14:11:39Zhttps://git.lysator.liu.se/pikelang/pike/-/issues/1187GIMP (xcf) files with layers in overlay mode broken2009-04-16T14:11:39ZPeter BortasGIMP (xcf) files with layers in overlay mode brokenImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=1187
Reported by David Hedbor, Idonex / Real Networks <david@hedbor.org>
Layers in xcf files that use the overlay method are oddly broken. Seems
like the alpha channel is...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=1187
Reported by David Hedbor, Idonex / Real Networks <david@hedbor.org>
Layers in xcf files that use the overlay method are oddly broken. Seems
like the alpha channel is ignored or something.Pike 7.0https://git.lysator.liu.se/pikelang/pike/-/issues/1167XCF decoder cannot decode "multiply" layers correctly2020-02-29T17:53:47ZPeter BortasXCF decoder cannot decode "multiply" layers correctlyImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=1167
Reported by @zino
The XCF decoder cannot decode "multiply" layers correctly. Attaching exmple
xcf and screenshots from Gimp and PV.Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=1167
Reported by @zino
The XCF decoder cannot decode "multiply" layers correctly. Attaching exmple
xcf and screenshots from Gimp and PV.Pike 7.2https://git.lysator.liu.se/pikelang/pike/-/issues/1076Rotation of an image of size 0 causes segfault.2009-04-16T14:11:39ZPeter BortasRotation of an image of size 0 causes segfault.Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=1076
Reported by Anders Johansson <anders@roxen.com>
```
Pike v7.0 release 141 running Hilfe v2.0 (Incremental Pike Frontend)
> Image.Image(17,0)->rotate(17);
zsh: 32118 ...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=1076
Reported by Anders Johansson <anders@roxen.com>
```
Pike v7.0 release 141 running Hilfe v2.0 (Incremental Pike Frontend)
> Image.Image(17,0)->rotate(17);
zsh: 32118 segmentation fault (core dumped) pike
```Pike 7.0https://git.lysator.liu.se/pikelang/pike/-/issues/984Image.Color and Colors.parse_color parses HSV differently2009-04-16T14:11:39ZPeter BortasImage.Color and Colors.parse_color parses HSV differentlyImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=984
Reported by Martin Nilsson, IDA <nilsson@pike.ida.liu.se>
```
> Colors.parse_color("@128,50,50");
Result: ({ /* 3 elements */
49,
79,
...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=984
Reported by Martin Nilsson, IDA <nilsson@pike.ida.liu.se>
```
> Colors.parse_color("@128,50,50");
Result: ({ /* 3 elements */
49,
79,
253
})
> Image.Color("@128,50,50")->rgb();
Result: ({ /* 3 elements */
63,
127,
72
})
```Pike 7.2https://git.lysator.liu.se/pikelang/pike/-/issues/982Image.Color may dump core on "grey"-input2009-04-16T14:11:39ZPeter BortasImage.Color may dump core on "grey"-inputImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=982
Reported by Martin Nilsson, IDA <nilsson@pike.ida.liu.se>
```
Pike v7.1 release 21 running Hilfe v2.0 (Incremental Pike Frontend)
> Image.Color("grey00");
Result: "û"...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=982
Reported by Martin Nilsson, IDA <nilsson@pike.ida.liu.se>
```
Pike v7.1 release 21 running Hilfe v2.0 (Incremental Pike Frontend)
> Image.Color("grey00");
Result: "û"
> Image.Color("grey99");
/home/nilsson/Pike/7.1/src/pike_types.c:153: Fatal error:
Error in type string 32.
Attempting to dump backlog (may fail)...
Backtrace at time of fatal:
-:1: ___Foo4711()
/home/nilsson/Pike/pike/7.1.21/lib/modules/Tools.pmod/Hilfe.pmod:103:
do_evaluate("mixed ___Foo4711() { return
(mixed)(Image.Color(\"grey99\"));
}\n",1)
/home/nilsson/Pike/pike/7.1.21/lib/modules/Tools.pmod/Hilfe.pmod:603:
parse_statement("Image.Color(\"grey99\");")
/home/nilsson/Pike/pike/7.1.21/lib/modules/Tools.pmod/Hilfe.pmod:381:
do_parse()
/home/nilsson/Pike/pike/7.1.21/lib/modules/Tools.pmod/Hilfe.pmod:224:
add_buffer("Image.Color(\"grey99\");\n")
/home/nilsson/Pike/pike/7.1.21/lib/modules/Tools.pmod/Hilfe.pmod:623:
add_input_line("Image.Color(\"grey99\");\n")
/home/nilsson/Pike/pike/7.1.21/lib/modules/Tools.pmod/Hilfe.pmod:703:
create()
Hilfe: StdinHilfe()
Abort (core dumped)
```Pike 7.2https://git.lysator.liu.se/pikelang/pike/-/issues/958found a file that causes segmentation fault in Image.load2009-04-16T14:11:39ZPeter Bortasfound a file that causes segmentation fault in Image.loadImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=958
Reported by Mirar , Idonex Heavy Industries <mirar@roxen.com>
```
> Image.load("breaks_tifflib.jpg");
zsh: segmentation fault pike
```Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=958
Reported by Mirar , Idonex Heavy Industries <mirar@roxen.com>
```
> Image.load("breaks_tifflib.jpg");
zsh: segmentation fault pike
```Pike 7.2https://git.lysator.liu.se/pikelang/pike/-/issues/626PNG decode coredumps on malformed images2009-04-16T14:11:39ZPeter BortasPNG decode coredumps on malformed imagesImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=626
Reported by Chris Jantzen, Maybe.Net <chris@maybe.net>
On malformed images (specifically from gd), the PNG decode will dump core.
Following patch fixes the issue:
``...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=626
Reported by Chris Jantzen, Maybe.Net <chris@maybe.net>
On malformed images (specifically from gd), the PNG decode will dump core.
Following patch fixes the issue:
```
diff -u -r1.31 png.c
--- src/modules/Image/encodings/png.c 2000/05/07 00:05:10 1.31
+++ src/modules/Image/encodings/png.c 2000/10/28 17:25:22
@@ -791,6 +791,7 @@
if (x)
x--,n--,*(d1++)=ct->u.flat.entries[CUTPLTE(((*s)>>4)&15,mz)].color;
if (x)
x--,n--,*(d1++)=ct->u.flat.entries[CUTPLTE((*s)&15,mz)].color;
s++;
+ if (n<2) break;
if (!x) x=width;
}
else
```
(hope that doesn't get too mangled by netscape)Pike 7.0https://git.lysator.liu.se/pikelang/pike/-/issues/8204Count memory used by Image.Image objects.2020-03-06T10:52:19ZPeter BortasCount memory used by Image.Image objects.Imported from https://youtrack.roxen.com/issue/PIKE-204
Reported by @grubba
Image.Image does not have a `gc_recurse` callback, and thus `Pike.count_memory()` will not count the memory used to store the actual image.Imported from https://youtrack.roxen.com/issue/PIKE-204
Reported by @grubba
Image.Image does not have a `gc_recurse` callback, and thus `Pike.count_memory()` will not count the memory used to store the actual image.https://git.lysator.liu.se/pikelang/pike/-/issues/8170Former Fix task of PIKE-169 (#8169). See it for details.2020-03-06T10:52:35ZPeter BortasFormer Fix task of PIKE-169 (#8169). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-170
Reported by @grubba
Blocking [PIKE-169](#8169)Imported from https://youtrack.roxen.com/issue/PIKE-170
Reported by @grubba
Blocking [PIKE-169](#8169)https://git.lysator.liu.se/pikelang/pike/-/issues/8168Former Investigate task of PIKE-169 (#8169). See it for details.2020-03-06T10:53:04ZPeter BortasFormer Investigate task of PIKE-169 (#8169). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-168
Reported by @grubba
Blocking [PIKE-169](#8169)Imported from https://youtrack.roxen.com/issue/PIKE-168
Reported by @grubba
Blocking [PIKE-169](#8169)https://git.lysator.liu.se/pikelang/pike/-/issues/8147Former Do it. task of PIKE-146 (#8146). See it for details.2020-03-06T10:53:18ZPeter BortasFormer Do it. task of PIKE-146 (#8146). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-147
Reported by @grubba
Blocking [PIKE-146](#8146)Imported from https://youtrack.roxen.com/issue/PIKE-147
Reported by @grubba
Blocking [PIKE-146](#8146)https://git.lysator.liu.se/pikelang/pike/-/issues/8146Recent versions of Freetype have removed freetype-config. Use pkg-config free...2020-03-06T10:53:35ZPeter BortasRecent versions of Freetype have removed freetype-config. Use pkg-config freetype2 instead.Imported from https://youtrack.roxen.com/issue/PIKE-146
Reported by @grubbaImported from https://youtrack.roxen.com/issue/PIKE-146
Reported by @grubba