{"id":744,"date":"2009-02-24T16:15:02","date_gmt":"2009-02-24T08:15:02","guid":{"rendered":"http:\/\/www.whoisandrewwee.com\/?p=744"},"modified":"2009-02-25T22:29:30","modified_gmt":"2009-02-25T14:29:30","slug":"tweetdeck-users-read-this","status":"publish","type":"post","link":"http:\/\/whoisandrewwee.com\/social-networking\/tweetdeck-users-read-this\/","title":{"rendered":"TweetDeck Users Read This…"},"content":{"rendered":"
I’ve discovered a major problem that plagues Tweetdeck users who use the free Twitter client to access and post microblogging updates. TweetDeck is bugged by a fairly major issue which will require a solution pretty soon.<\/p>\n
Background: I’m an active Twitter user and have been using what I would consider the best Twitter client, TweetDeck, for a couple of months.<\/p>\n
Sure it’s had some weird idiosyncrasies like having to shut it down so I could run more bandwidth-intensive applications or MMPOGs on my system, but on the whole, it’s been a pleasant experience (read my earlier review<\/a>)<\/p>\n I may or may not be the typical Tweetdeck user – here’re my usage habits:<\/p>\n As a result, it’s not uncommon to wake up to 500+ tweets during the 6 hours I’m sleeping.<\/p>\n Particularly today, my machine crawled to a grinding crawl, and pulling up the Windows Task Manager (hit alt-ctrl-delete to see this):<\/p>\n <\/p>\n Coming in at #1, TweetDeck with a pretty monstrous 334 MB of memory usage (followed by Firefox where I had about 30 tabs open).<\/p>\n And a screenshot a few minutes later:<\/p>\n <\/p>\n So I’ve had to shut TweetDeck down, as almost every other application was pretty unusable.<\/p>\n Dave Davis AKA RedFly<\/a> mentioned that TweetDeck’s memory leak issue had been Dugg (the orig post has since been removed) though I found another blog post mentioning the leak<\/a>.<\/p>\n There’s speculation that the Adobe AIR runtime is responsible for the memory leak. Others are saying TweetDeck is the culprit.<\/p>\n With some probing, I saw mentions on the TweetDeck posterous\/wall\/blog<\/a> or on TweetDeck founder\/developer Iain Dodsworth’s twitter stream<\/a>.<\/p>\n In response to a user’s complaint that TweetDeck had swallowed 1.4 GB of ram, Iain responded: “yep will fix ASAP – in meantime just restart app to release memory and go back to starting memory usage amount”<\/span><\/span><\/p>\n Iain has also mentioned incremental upgrades are on the way with a major release scheduled soon. Hopefully, Iain will kill the memory problem dead.<\/p>\n I still think TweetDeck is still the best fraking Twitter app out there, especially if you’re following more than 50 twitter users. The memory leak issue should be addressed soon.<\/p>\n –<\/p>\n Update:<\/strong> If you leave TweetDeck on 24-7, it looks like you can keep a maximum of 500 backlogged\/unread tweets, so there is a buffer for 500 tweets. As new ones come on, the old ones fall off your viewable page.<\/p>\n –<\/p>\n\n