Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New Twitter Has Become Browser Poison

mikecanex.wordpress.com

Post reply on HN
Print view View original

71–80 of 108 posts

Re: New Twitter Has Become Browser Poison

#71

Post by comex »

petdog wrote: post #54
redthrowaway wrote: post #31

Earlier quoted context omitted.

I routinely leave my browser open for days on end and simply cycle through tabs, closing and opening new ones as needed, with usually ~10 open at a given time. I, too, noticed that firefox was eating up about half a gig of ram even when it wasn't doing anything, didn't have any youtube tabs open, etc. It got to the point where I would have to close firefox and restart after a day or two. Chrome fixed that. Now, I jus…

Now, maybe I'm to blame here, using the nightly build of chromium, but webkit is a walking memory leak. Just for a comparison, I have the same amount of tabs on firefox and chromium and firefox is using 500mb of ram, while chromium is using 3.5 GIGABYTES. And I'm not even using it much. But really, the problem is easily reproducible. Just open whatever webkit based browser you want, and keep reloading the same modera…

Good thing Chrome kills the entire process hosting a tab when you close it.

Re: New Twitter Has Become Browser Poison

#72

Post by didip »

epi0Bauqu wrote: post #10

I've been keeping twitter open in its own Firefox browser on one screen (of three). It routinely refreshes itself and there is some kind of memory leak whereas after a day it is consuming about half a gig of memory, forcing me to kill and restart.

Endless pagination/Infinite scrolling is pretty much the definition of memory leak, no?

Re: New Twitter Has Become Browser Poison

#73

Post by sandofsky »

kragen wrote: post #69
russ wrote: post #27

Earlier quoted context omitted.

Try http://mobile.twitter.com

Yeah, I've been using it today. I want to love it but I can't. No DM count on the screen (to save three bytes?!), no user icons, no way to tell that I've gone over 140 characters.

Are you using a really low end user agent to try to access the site? I don't know what's turned off for lower end browsers, but I just tested in desktop Webkit. There's a character count in the upper right of the tweet box. There are user icons, unless you clicked the "images off" link.

As for total DM count, that isn't really possible right now. The app is just another API client, and the DM API endpoint only provides the last 20 DMs.

Re: New Twitter Has Become Browser Poison

#75

Post by anto1ne »

wizard_2 wrote: post #9

I noticed the same thing on my girlfriends CR-48, twitter wont scroll properly (studders) and everything else hangs a bit. She filed a bug report with google chrome os support, but I suspect twitter is doing a lot of heavy stuff in the background.

here's a bug open at chrome : http://code.google.com/p/chromium/issues/detail?id=69777 but the issue is at twitter really. I noticed it a few days ago too, and chrome didn't update.

Re: New Twitter Has Become Browser Poison

#76

Post by kragen »

sandofsky wrote: post #73
kragen wrote: post #69

Earlier quoted context omitted.

Yeah, I've been using it today. I want to love it but I can't. No DM count on the screen (to save three bytes?!), no user icons, no way to tell that I've gone over 140 characters.

Are you using a really low end user agent to try to access the site? I don't know what's turned off for lower end browsers, but I just tested in desktop Webkit. There's a character count in the upper right of the tweet box. There are user icons, unless you clicked the "images off" link. As for total DM count, that isn't really possible right now. The app is just another API client, and the DM API endpoint only provid…

No, FF3.

Re: New Twitter Has Become Browser Poison

#77

Post by russ »

russ wrote: post #21

Over time, NewTwitter does incur a large memory footprint. I've been traveling for a month and haven't looked into the problem in depth, but I'd bet the major culprit is our aggressive caching techniques. It's also worth investigating the number of polls and their frequencies. Timeline refreshes are dropped back to 90 seconds when the tab isn't focused, but not sure about other ones. As most people have reported, inf…

Update: Apparently there was a regression introduced last week that has exacerbated this problem. Some folks are working on a fix.

Re: New Twitter Has Become Browser Poison

#78

Post by catshirt »

russ wrote: post #21

Over time, NewTwitter does incur a large memory footprint. I've been traveling for a month and haven't looked into the problem in depth, but I'd bet the major culprit is our aggressive caching techniques. It's also worth investigating the number of polls and their frequencies. Timeline refreshes are dropped back to 90 seconds when the tab isn't focused, but not sure about other ones. As most people have reported, inf…

With respect, why exactly is total script size 912kb minified? That seems unexpectedly high. Likely not the root of the problem at hand, just curious.

Also interested in what you plan to do to alleviate massive DOM issues, if you could share. Typically an overlooked point of performance.

Re: New Twitter Has Become Browser Poison

#79

Post by j_baker »

rhizome wrote: post #14

The thing I noticed in the slow new Twitter is that typing a new status seems to involve continuous autofill-like behavior for each character typed, which seemed to introduce round-trip lag (or javascript-parsing, or...) and causes characters to appear at a rate of ~1/second. Unusable. And this is one way that dominant sites fall: business considerations are given priority over the user experience. Maybe they just ha…

Or it could also point to a "Hey, this is different. I don't like change!" reaction that you always get when you change something's UI.

Re: New Twitter Has Become Browser Poison

#80

Post by saurik »

russ wrote: post #21

Over time, NewTwitter does incur a large memory footprint. I've been traveling for a month and haven't looked into the problem in depth, but I'd bet the major culprit is our aggressive caching techniques. It's also worth investigating the number of polls and their frequencies. Timeline refreshes are dropped back to 90 seconds when the tab isn't focused, but not sure about other ones. As most people have reported, inf…

Infinite scroll is also a way to make scrolling infuriating, especially if you are wanting to click links and fan out from that location: it forces you to avoid your browser's carefully designed history stack like the plague (opening new tabs or windows for navigation instead) lest you lose your incredibly valuable document you've carefully been scrolling down in (and which is now so large it is threatening to cripple your browser anyway). What happened to normal "next page" paradigms? Does user testing really show that infinite scroll is better?
Post reply on HN