Samuel
@samuel.fm
this react navigation thing is killing me. why does it take so much memory now :/
3 33Samuelohhhhhh. 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 15Samuel@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 2025I know this commit! I like this commit 😅
Samuelbasically 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 Bestaatthat 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
Kuba Suder 🇵🇱🇺🇦Uh… that's… that's bad
1 2Kuba Suder 🇵🇱🇺🇦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 🫠
1
Barry DorransIs this why everything is so slow now?
1 2
Andri ÓskarssonReact Navigation has always been a mixed bag for me. It mostly does what I want and it looks good on all platforms.
But, I have often wished for something simpler. Maybe @bacon.bsky.social has some grand plans for the Expo router
1