basically turns out the only reason this app ever worked at…

Samuel 8 Jul 2025

this react navigation thing is killing me. why does it take so much memory now :/

Samuel 8 Jul 2025

ohhhhhh. it’s the pop behaviour change I think. looks like the implicit screen pop behaviour of v6 was accidentally doing garbage collection when you were clicking around the app lmao v7 always adds new screens, so memory use just keeps building

1 1 15

Samuel 8 Jul 2025

@mackuba.eu pretty sure the behaviour change you were looking for was the exact thing that caused the perf issue 😭

Kuba Suder 🇵🇱🇺🇦@mackuba.eu· 7 Jul 2025

I know this commit! I like this commit 😅

1 16

Samuel

@samuel.fm

basically turns out the only reason this app ever worked at all was due to completely jank unintentional behaviour lmao. we need to reenable the jank for it not to explode

6 3 36

Michel Bestaat 8 Jul 2025

that totally sucks, you find a bug that's been there for a long time, you fix it and then you find that the bug actually made things work, hang in there

1 4

Juho Vepsäläinen 8 Jul 2025

It's this but as a bug. xkcd.com/2347/

Dependency

xkcd.com

Bossett 8 Jul 2025

I paid for all these giblibytes and now you're telling me I don't get to use them??

Kuba Suder 🇵🇱🇺🇦8 Jul 2025

Uh… that's… that's bad

1 2

Kuba Suder 🇵🇱🇺🇦8 Jul 2025

So the good news is, if you manage to figure out a better way to do this, that could decrease the memory use of my Safari a lot 🫠