twitter: how many levels of high-risk javascript bloat are you on? facebook: like,, about 240 meg and two subframes for the home page right now, my dude twitter: you are like a little baby, watch this twitter: <expanding a tweet from the main timeline locks up the tab>
-
-
Replying to @chaosprime
have profiled Twitter memory usage a bit. it starts near 50mb on a fresh page load and creeps up at the rate of 10-15mb per minute forever until you refresh the page. the memory leaks are a design feature I think. maybe they get to serve new ads when you refresh?
2 replies 0 retweets 11 likes -
Replying to @danlistensto @chaosprime
honestly this conspiratorial mindset seems like the only sensible explanation that 10% of the time the tweet input will get so slow, presumably from memory leaks, that I'll have to refresh the page
1 reply 0 retweets 3 likes -
at the least it's plausible explanation of why Twitter might not be prioritizing a bugfix: "we can't fix this known memory leak because our advertising analytics numbers will go down and management will think we screwed something up"
1 reply 0 retweets 3 likes -
Replying to @bnjmnhndrsn @chaosprime
it kinda fits enough that I'm not 100% sure I'm just being paranoid. the other thing is it's probably relatively hard to fix, very multi-faceted problem touching a ton of code, and generally not worth it cuz page refresh is a thing so what's the problem really?
1 reply 0 retweets 1 like -
Replying to @danlistensto @chaosprime
yes true. but we mustn't let those voices of sense in our heads win out!
1 reply 0 retweets 5 likes
I would never, lead with paranoia, renegotiate to reason only under duress.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.