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.
I've noticed the same thing on mine. It seems like the site is only functional when you first load it. After new tweets start rolling in, it becomes worse and worse. I don't think it's the fault of the CR-48, I think we're just seeing the effects worse on this hardware.
Same thing here. It's not ChromeOS-related? I note the same problem in Chromium.
This is the least scientific analysis I think anyone could get away with. Why doesn't the author just profile the Twitter page to see how much time his CPU spends executing Javascript code and how much memory it consumes while running?
The author mentioned Shockwave. I don't think he's too technical a user.
Firefox has crazy memory leaks. Proof? This was the case with Firefox 2 but now it just seems like this is part of their reputation and is not necessarily grounded in fact.
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 moderately big page. Ram goes up, never to return. That works with a trivial program that embeds webkit via gtk, too.
Or you can just look at the commits on webkit: a couple of leaks fixes every week.
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.
Are you using FF4 beta? I've had two pages of newtwitter open in app tabs for months now and never ever have problems with it.
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.
Are you using FF4 beta? I've had two pages of newtwitter open in app tabs for months now and never ever have problems with it.
I can't help thinking that the tacked-on whine about this is why people want iPads and not PCs would make more sense if this post were not about a web-app that would probably slow down any tablet it was accessed on.
The "the tacked-on whine" as you call it was referring to having to check for the latest version of this that and the other bloody plug-in. Point being, people just Want Shit To Work.
This is the least scientific analysis I think anyone could get away with. Why doesn't the author just profile the Twitter page to see how much time his CPU spends executing Javascript code and how much memory it consumes while running?
The author mentioned Shockwave. I don't think he's too technical a user.
I dropped Shockwave in there as yet another example of something else that needs to be checked for the latest version. Not every plug-in is good about saying there's an update and most of the time the update notifications come in the middle of getting work done, so people tend to disable that distraction.
The point of my post is also this: Something changed in the behavior of New Twitter. None of this happened when I was first given access to NT months ago. The problems seemed to crop up simulataneously -- coincidentally -- with my moving to Opera 11 beta. The problems have since spread to all 3 of the browsers I wound up cycling through. So I think Twitter changed something on their end and are unaware of the ripple effect on some users. Someone, on Twitter, suggested they were once polling every 90 seconds in the beginning and now that the switch is complete, we are getting "live streaming." That might be too much for some systems to handle. Perhaps a user option to throttle back polling? [typo edit]
The author mentioned Shockwave. I don't think he's too technical a user.
I dropped Shockwave in there as yet another example of something else that needs to be checked for the latest version. Not every plug-in is good about saying there's an update and most of the time the update notifications come in the middle of getting work done, so people tend to disable that distraction.
Yeah - but New Twitter has absolutely nothing to do with Shockwave.