Created attachment 125014 [details] example mime message (7bit, so editor readable) SUMMARY kmail crashes every time I try to open this message. I stripped down the real message (daily report) to this minimal empty html table with one css style. STEPS TO REPRODUCE 1. kmail --view attached-mime.eml OBSERVED RESULT Crash EXPECTED RESULT Should show the message window (empty html table) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.4.10-arch1-1 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Appeared (I think) with kmail 5.13.0 and still exists in kmail 5.13.1 ADDITIONAL INFORMATION I tried with all modules switched off in kmail but it still crashes. Host uses german localization. Original message is a daily report with html and images as mime multipart. I tried the minimal crash triggering html as mime multipart and as plain html text. Both crashes kmail here. If I can provide more helpfull information, please let me know. But I would be very thankful if someone at least could try to open the mime message and reports whether this is reproducible or just local here. Thanks in advance For convenience, here is the full content payload of the mime file: ------------------- <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <style type="text/css"> tr, td { border-width: 0px; } </style> </head> <body> <table> <tr> <td></td> </tr> </table> </body> </html> ------------------- If you split the css style like this (order does not matter): ------------------- tr { border-width: 0px; } td { border-width: 0px; } ------------------- Or remove the td tag in the table it works.
Created attachment 125015 [details] crashlog (unfortunately without debug information)
Qt version ? It doesn't crash here.
QT 5.14.0 Ok, I will continue to inspect my environment here and report back.
Created attachment 125016 [details] Crashlog with Qt debuging (qt5-base-debug + messagelib)
Created attachment 125017 [details] Crashlog with Qt debuging (qt5-base-debug, qt5-webengine-debug, messagelib)
I fixed this in https://bugreports.qt.io/browse/QTBUG-80496
Thanks, yes that was it.