Crash Report
Crash Report
Opening this post (PC CD-ROM games at the hotel I stayed at) by hulemy@ani.social causes the app to crash every time. The same doesn't seem to happen in other apps (tested Sync and Voyager). Viewing the post in the feed is fine though (try here).
You're viewing a single thread.
I tested a few more apps. Here's my summary:
Visit beehaw.org/c/gaming :
- Eternity: post shows up
- Sync: post shows up
- Voyager: post shows up
- Jerboa: post doesn't show up
- Boost: post shows up
- Connect: post shows up
Open post via beehaw.org/c/gaming :
- Eternity: app crashes completely
- Sync: displays post
- Voyager: displays post
- Jerboa: not applicable
- Boost: displays post initially, then either crashes to previous post or completely
- Connect: displays post
Open post via link:
- Eternity: crashes to previous post
- Sync: displays post
- Voyager: displays post
- Jerboa: opens post externally in browser
- Boost: displays post initially, then either crashes to previous post or completely
- Connect: displays "Error: unknown" and "1471762@infosec.pub unknown" (instance name infosec.pub changes when opened via a different instance)
OP of that post here. It breaks on Boost for Reddit too, I made the post using the web interface. This is the content of the post:
   I don't know what causes it, although it shows some  symbols in Boost before crashing.
Loaded fine the first time until we tried fullscreening the initial image. The unknown symbols seems to be the alt text for that first image.
I can see and open the post just fine in Jerboa. No issues for me!