On Wed, Apr 15, 2020 at 5:46 PM Eli Zaretskii <eliz@gnu.org> wrote:

> 6 is too much, I think.  Are you saying that inside w32_frame_delay,
> before division by 100, the value is 600?

Yep.


Thread 1 hit Breakpoint 2, w32_frame_delay (pBitmap=pBitmap@entry=0x5af22f0,
    frame=frame@entry=0) at w32image.c:205
205     {
(gdb) n
212       GdipGetPropertyItemSize (pBitmap, PropertyTagFrameDelay, &size);
(gdb) n
215       propertyItem = malloc (size);
(gdb) n
216       if (propertyItem != NULL)
(gdb) n
[New Thread 18512.0x55f4]
219           GdipGetPropertyItem (pBitmap, PropertyTagFrameDelay, size,
propertyItem);
(gdb) n
220           delay = propertyItem[frame].length / 100.0;
(gdb) p frame
$1 = 0
(gdb) p propertyItem[0].length
$2 = 600
(gdb) n
221           if (delay == 0)
(gdb) p delay
$3 = 6
(gdb)


After setting w32-use-native-image-API to nil and clearing the cache,

 (image-metadata
  (find-image
   '((:type gif :file "/path/to/CavernousFeistyArach
nid-size_restricted.gif"))))

=>

(count 150 delay 0.1 extension-data
       (249 "^E^@Y" 0 "^A^@^@" 255 "NETSCAPE2.0"))