Strange freezes with AmigaGuide documents

Hi,

I have strange issues when viewing large AmigaGuide documents on my X5000 with MultiView.

Resizing an AmigaGuide document displayed in MultiView freezes AmigaOS's GUI. The OS is not completely dead as TuneNet is still playing.

There is no GrimReaper and no output on Serial.

The easiest way for me to reproduce the freeze is to open "Includes_and_Autodocs_2.0" from Amiga Developer CD 2.1 and go to "Includes (dir)" -> "hardware (dir)" -> "cia.i" and resize the window.

MultiViewer also randomly freezes the system when working with AmigaGuide files. But I normally do not use MultiViewer, and I did not find a sure way to reproduce the freezes yet.

The files MultiView and DataTypes/AmigaGuide are the same as the ones from Update 2 archive.

System details:
AmigaOne X5000/20
8 GB RAM
240 + 120 GB SSD
Radeon RX 550
ESI @Julia
SIL 3512

AmigaOS 4.1 Update 2 + Enhancer V2.2

Any ideas?

Thank you,
Flynn

@FlynnTheAvatar

Does the document contain links to external files - text or pictures?

If so, it's probably a known and reported bug.

If you can confirm the above, I can add a reference to this thread to the bug report.

Best regards,

Niels

@nbache

You're right—the initial AmigaGuide document does contain multiple links to external files.

The file that triggers the crash is a basic text file with no further links. Interestingly, it only crashes when accessed via one of the links in the original AmigaGuide document—not when opened directly.

I hope that helps clarify the issue.

If this aligns with the known bug, would you happen to know when a fix might be expected? Thanks again!

@FlynnTheAvatar

Yeah, this does sound exactly like the situations described in the bug report. I'll add a reference to this thread for an extra clue for some bugfixer.

And no, sorry, can't say anything about timeframe.

Best regards,

Niels

@nbache

Thank you very much for the update.

I found the first mentioning of this bug from 2011. So it is best not to hold my breath until it is finally fixed.

@FlynnTheAvatar

Let's hope another update to the bug report catches the attention of someone who happens to know a solution. But of course there are a number of medium or minor bug like this competing for that attention.

Best regards,

Niels