search

jens-maus / yam

:mailbox_with_mail: YAM (short for 'Yet Another Mailer') is a MIME-compliant open-source Internet email client written for Amiga-based computer systems (AmigaOS4, AmigaOS3, MorphOS, AROS). It supports POP3, SMTP, TLSv1/SSLv3 connection security, multiple users, multiple identities, PGPv2/v5 encryption, unlimited hierarchical folders, an ARexx interface, etc...
https://yam.ch
GNU General Public License v2.0
61 stars 18 forks source link

YAM stops working properly ater opening mail with html body and image attachment #687

Closed Jonson26 closed 3 years ago

Jonson26 commented 3 years ago

Submission type

YAM version

YAM210dev-20201227-9b4aa0

Used operating system

Used Amiga system

Amiga 1200 ACA1233n40 Lucent Hermes chipset wifi card MiamiDX AmiSSL 4.7

Expected behaviour you didn't see

[...]

Unexpected behaviour you saw

YAM starts behaving erratically without crashing completely. The mouse occasionally lags, most menus don't work and closing the progarm is not possible most of the time. (I only managed to do it once, and after starting it up again the OS crashed.) Moving or resizing the window isn't working at all too. On the other hand, clicking on drawers and opening messages in the small preview box works. Opening messages in a separate window does not work. After reboot everything works as normal again.

Steps to reproduce the problem

Open an email with HTML body and images attached. I can send you one that definitely triggers the bug.

Jonson26 commented 3 years ago

Workaround found: Disable html-to-plaintext rendering in preview.

Jonson26 commented 3 years ago

Nevermind. Issue still persists.

Jonson26 commented 3 years ago

If it helps, I found that when the issue happens, it also messes up other MUI-based programs, which either crash or fail to load entirely.

Jonson26 commented 3 years ago

Found an actual fix this time! Installing Fblit has so far prevented this from happening, despite me opening numerous emails that would have crashed the program before. This suggests, that the issue is somehow rooted in the graphical system. In any case, if anyone else is having a similar issue on a classic system, try installing Fblit or one of the native RTG drivers.