It's not lemmy.world, there's a bad post that is crashing sync for users across instances. It's a sync bug.
It was reported here https://midwest.social/post/9381826 but the comments in that will now crash sync too.
๐
Welcome to the official Sync for Lemmy community.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1- No advertising or spam.
All types of advertising and spam are restricted in this community.
Artwork and community banner by: @MargotRobbie@lemmy.world
It's not lemmy.world, there's a bad post that is crashing sync for users across instances. It's a sync bug.
It was reported here https://midwest.social/post/9381826 but the comments in that will now crash sync too.
Ah. So it's just coincidence that lemmy.world updated to 0.19 today too?
Yes, sh.itjust.works updated Friday and I hadn't encountered anything until now
I've been running .19 on my instance for a while now and recently upgraded to .19.3 and haven't had any crashing on Sync.
Thanks. I couldn't figure out why my Sync was crashing all day
This looks like it might be a corrupted database entry.
Trying to post a link to the image using the old.lemmy.world interface causes a problem as well
~~It looks like someone has posted a malformed image that is causing the issue.~~
It's this post
It did something for me. Not exactly a crash but it refreshed back to the main page but a few posts away from this one.
Oh, now I see the image. That post was fucking with me too. Once I was able to hide that post the crashing stopped.
Not exactly a crash but it refreshed back to the main page but a few posts away from this one.
That's what happened to me. Repeated attempts to load it made a prompt to clear cache appear. I haven't had a full crash yet. Maybe there's other offending posts. This one is in thee communities though so it could hit a lot of people.
Edit: it's something to do with the user. They made another post in cryptography that breaks sync for me too.
I'd be cautious.
These malformed images may be malicious.
A malformed image should not cause a crash. I'm not sure what libraries Sync uses for this stuff, but the bug should be reported upstream (assuming it's not just some exception mishandling going on in Sync.)
If you block the user, it seems to fix the problem,, but you'll have to block them on another app, or via browser, obviously.
Pain in the ass