Closed Bug 1030 Opened 26 years ago Closed 26 years ago

Animated GIF that crashes NGLayout win32

Categories

(Core Graveyard :: GFX, defect, P3)

Product:
Core Graveyard
Component:
GFX
Platform:
x86
Windows 95
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 1031

People

(Reporter: marni894, Assigned: michaelp)

References

(
URL
)

Details

Bugreport for NGLayout win32 nighly build 19981008.
The GIF image on the page in the URL crashes with the following error displayed:

VIEWER orsakade ett ogiltigt sidfel i
modul RAPTORGFXWIN.DLL på adress 014f:00470fb8.
Register:
EAX=0125ef00 CS=014f EIP=00470fb8 EFLGS=00010246
EBX=00abfcbe SS=0157 ESP=00abfb98 EBP=00abfbbc
ECX=dddddddd DS=0157 ESI=00008ce2 FS=4aa7
EDX=0125ef00 ES=0157 EDI=00abfc74 GS=769f
Byte på CS:EIP:
ff 51 10 89 45 f8 83 7d f8 00 75 23 8b 45 e8 3b
Stackdump:
0125ef00 00abfba8 30019ab1 00000000 00008ce2 0125ae60 00000000 00000000 0125ef00
00abfbe8 00471120 0125aec0 0125aa00 0125ef00 00001fcd 10257f50

Sorry for the Swedish, but most is universal. My computer is an AMD K6 with 64MB
RAM running in 1024x768 with 24-bits truecolour.
Summary: Animated GIF that crashes NGLayout win32 → ss:Animated GIF that crashes NGLayout win32
Putting on ss: radar
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
doesn't crash anymore on 11/23a builds of viewer.exe or xpviewer.exe on win95.
Marking resolved fixed.
Verified fixed.
Status: VERIFIED → REOPENED
Summary: ss:Animated GIF that crashes NGLayout win32 → Animated GIF that crashes NGLayout win32
ok, so it no longer crashes. it still doesn't behave the same as in navigator
though, so i'm reopening it.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: FIXED → DUPLICATE
*** This bug has been marked as a duplicate of 1031 ***
Status: RESOLVED → VERIFIED
Verified that present behavior in 10.27.99 build on Mac OS & Win32 is a duplicate
of 1031 (animated GIF that ceases to animate.)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.