@awoo @tobi what I meant was do you remember how many days / weeks ago on the snapshot you first noticed this lockup happening?

@awoo @tobi what I meant was do you remember how many days / weeks ago on the snapshot you first noticed this lockup happening?

@awoo @tobi or did i misunderstand ?

@kim @tobi oh, that! probably like 2 weeks ago or something (specifically, april 28th is when I switched back to stable because of that)

@awoo @tobi noted! useful to know, thank you

@kim @tobi you're welcome ^^

should you need me to test if it works by then or not, feel free to let me know

@awoo @tobi got some more Qs for ya

• so this issue is only appearing on the snapshot? or in latest release too?
• when you switched back to the regular releases to avoid it on 28th April, how long had it been happening? for a few days? or weeks?

@kim @tobi here are some As :3

• this issue is only occurring on the snapshots, not in 0.19.0 or 0.19.1 stable.
• it had been happening for a day or two already back then, can't exactly recall...

@awoo @tobi this is very useful! and very likely narrows it down to what i was expecting (my big timeline code rewrite heh)

@awoo @tobi i've got a change which should fix the lockup issue, or at the very least fix a potential lockup. though if my hunch is correct it means your instance might be failing to preload timeline caches, in which case look out for some error logs along the lines of "error loading statuses:"

change is here: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4182

@kim @tobi oh, forgot to add: I'll test this in around half an hour or so (once I'm back from getting groceries) and let you know if something still breaks after a while or if it works now ^^

edit at 20:48: just updated to the latest commit again ^^

@awoo @tobi fingers crossed it works out