DiskImageDevice Problem... [SOLVED]

Got it also after switching themes and behold - if it is Amiga then the bug is weird:

In GUI preferences under Gadgets=>General>Background texture - if you don't have a texture (the default theme has one) and just use a solid color then DiskImageGUI crashes!

________

X1000 user

Yep, I can confirm setting 'GUI preferences under Gadgets=>General>Background texture' to no texture/image DiskImageGUI crashes:

Dump of context at 0xFFC0C3E0
Trap type: DSI exception
Machine State (raw): 0x0002F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Instruction pointer: 0x7FDEE20C
Crashed process: DiskImageGUI (0x5E976B30)
0: 018740D4 60198E90 00000002 5F8F5968 60198E98 60198FC0 60198FC0 0000003D
8: 00000075 00000004 5F8F574C 5F7C4B68 28844448 5BA145F8 00000140 60199060
16: 00000000 60199074 6019906C 000000C8 60198FB8 6FEAA978 6FF55140 5DCC6498
24: 0000010A 6FE7D010 60198E98 00000000 60198FC0 00000298 02179704 5F8F5968
CR: 48844444 XER: 20000002 CTR: 7FDEE1DC LR: 018740D4
ESR: 00000000
DEAR: 00000040
mcsrr0: 0x00000000
csrr0: 0x00000000
...
Registers pointing to code:
r0 : native kernel module Kickstart/kernel.debug+0x000740d4
r30: native kernel module Kickstart/kernel.debug+0x00979704
ip : module CLASSES:window.class at 0x7FDEE20C (section 0 @ 0xE1E8)
lr : native kernel module Kickstart/kernel.debug+0x000740d4
ctr: module CLASSES:window.class at 0x7FDEE1DC (section 0 @ 0xE1B8)

Stack trace:
(0x60198E90) module CLASSES:window.class at 0x7FDEE20C (section 0 @ 0xE1E8)
(0x60198F30) native kernel module Kickstart/kernel.debug+0x000740d4
(0x60198F90) native kernel module Kickstart/graphics.library.kmod+0x000c20ec
(0x60199010) native kernel module Kickstart/graphics.library.kmod+0x0000e264
(0x60199040) module CLASSES:gadgets/layout.gadget at 0x7FDD7BEC (section 0 @ 0x5BC8)
(0x60199160) module CLASSES:gadgets/layout.gadget at 0x7FDDF598 (section 0 @ 0xD574)
(0x601991C0) module CLASSES:gadgets/layout.gadget at 0x7FDDB5C8 (section 0 @ 0x95A4)
(0x60199360) native kernel module Kickstart/intuition.library.kmod+0x0002144c
(0x601993C0) native kernel module Kickstart/intuition.library.kmod+0x000215f0
(0x60199440) native kernel module Kickstart/intuition.library.kmod+0x000219a4
(0x601994B0) native kernel module Kickstart/intuition.library.kmod+0x0000e8d4
(0x601994F0) native kernel module Kickstart/intuition.library.kmod+0x0000eb10
(0x60199580) native kernel module Kickstart/intuition.library.kmod+0x0007f7fc
(0x60199650) module CLASSES:window.class at 0x7FDE87B8 (section 0 @ 0x8794)
(0x60199840) module CLASSES:window.class at 0x7FDE9AC4 (section 0 @ 0x9AA0)
(0x60199B50) native kernel module Kickstart/intuition.library.kmod+0x0002144c
(0x60199BB0) native kernel module Kickstart/intuition.library.kmod+0x000215f0
(0x60199C30) native kernel module Kickstart/intuition.library.kmod+0x0000a2ac
(0x60199C40) module DiskImageGUI at 0x7FAF9394 (section 4 @ 0x8370)
(0x60199C60) module DiskImageGUI at 0x7FAF9214 (section 4 @ 0x81F0)
(0x60199C70) native kernel module Kickstart/intuition.library.kmod+0x0002144c
(0x60199CD0) native kernel module Kickstart/intuition.library.kmod+0x000215f0
(0x60199D50) native kernel module Kickstart/intuition.library.kmod+0x0000a3f4
(0x60199D60) native kernel module Kickstart/intuition.library.kmod+0x0000a034
(0x60199DD0) module DiskImageGUI at 0x7FAF850C (section 4 @ 0x74E8)
(0x60199DF0) module DiskImageGUI at 0x7FAF1FB4 (section 4 @ 0xF90)
(0x60199EB0) module DiskImageGUI at 0x7FAF1778 (section 4 @ 0x754)
(0x60199ED0) DiskImageGUI:_start()+0x3f0 (section 5 @ 0x3EC)
(0x60199F90) native kernel module Kickstart/dos.library.kmod+0x00025ecc
(0x60199FC0) native kernel module Kickstart/kernel.debug+0x00066aa8
(0x60199FD0) native kernel module Kickstart/kernel.debug+0x00066af0

Disassembly of crash site:
7FDEE1FC: 81430010 lwz r10,16(r3)
7FDEE200: 816AFFFC lwz r11,-4(r10)
7FDEE204: 836B0024 lwz r27,36(r11)
7FDEE208: A3AB0020 lhz r29,32(r11)
>7FDEE20C: 813B0040 lwz r9,64(r27)
7FDEE210: 7FBD5214 add r29,r29,r10
7FDEE214: 7D234B78 mr r3,r9
7FDEE218: 812900BC lwz r9,188(r9)
7FDEE21C: 7D2903A6 mtctr r9
7FDEE220: 4E800421 bctrl
Stack pointer (0x60198E90) is inside bounds
Redzone is OK (4)

@jabirulo

Thanks for the diagnosis. I was getting the same weird freeze with DiskImageGUI and adding a texture fixed it.

FYI. Since the InfoWindow class in the Enhancer Pack caused me a similar lockup problem I decided to retest it with a texture set in Prefs ... and that also resolves that problem. It works fine now too.

Hopefully that helps anyone else out with similar issues.

@all

Has this bug already been reported on the Hype forums?

@Raziel

No idea, but reporting third party bugs on the Hyperion forums is not generally a good idea, and niether product mentioned here is Hyperion product.

@broadblues

Oh right, i just thought it might be a general GUI problem

@Raziel

Quote:
Well it might be because I don't think me or Fredrik do things other than request standard system gadgets. But of course I'll have a look. There is one place in InfoWindow Class where I read the system GUI prefs, so I'll start looking there.

@Raziel

I reported it in the with the enhancer software folks.

Well now this is strange. I tried to isolate the problem, slimming the InfoWindow Class code to a bare minimum that just opens a window with a minimalistic layout, consisting of a single Label Image with text. This is all done in OM_NEW, no other class code is called. The result is the same: the system freezes up if the background texture is missing in the GUI prefs.

I've found that the freeze occurs during WM_OPEN, and it looks like the Window Class gets a problem when rendering the layout - although my layout contains just the one Label. If WINDOW_Layout points to an empty Layout Gadget, the window opens fine even without the background texture set. As soon as I LAYOUT_AddChild anything (of course I do that before opening the window), here comes the freeze.

So I'm really out of my depth and would appreciate any help or tips.