# Feedtools **URL:** \ **Category:** Rails\ **Created:** [March 21, 2006, 8:10pm UTC](https://www.ruby-forum.com/t/feedtools/84839 "2006-03-21T20:10:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![regularfry](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@regularfry](https://www.ruby-forum.com/u/regularfry)\ **Post date:** [March 21, 2006, 8:10pm UTC](https://www.ruby-forum.com/t/feedtools/84839/1 "2006-03-21T20:10:39Z")
Hi all, Is anyone else seeing silly amounts of segfaults with Feedtools? They’re regular enough to make it unusable, but I haven’t pinned down what’s triggering them yet. Here’s the error: > deadlock 0xb75970a8: run:-/usr/lib/ruby/1.8/timeout.rb:42: [BUG] Segmentation fault > ruby 1.8.3 (2005-06-23) [i486-linux] Naturally, that knocks over WEBrick, and causes 500 errors in Lighttpd. That ruby 1.8.3 is a reference to the fact that I’m on Ubuntu Breezy - it’s not so far otherwise been a problem. The only parts of the FeedTools API I’m using are FeedTools::Feed.open() and FeedTools::Feed#title. I’ve got feedtools 0.2.23 installed, and the database is sqlite3. Rails is 1.0. Any ideas? [sporkmonger.com](http://sporkmonger.com) seems to be down at the moment, so I can’t look there, but Google didn’t throw up anything relevant… ---
**Author:** ![regularfry](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@regularfry](https://www.ruby-forum.com/u/regularfry)\ **Post date:** [March 22, 2006, 4:56am UTC](https://www.ruby-forum.com/t/feedtools/84839/2 "2006-03-22T04:56:36Z")
Is it possible that the feed that you’re trying to open is not accessible and that’s why it it’s timing out? Does this happen with all feeds or one particular feed? ---
**Author:** ![regularfry](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@regularfry](https://www.ruby-forum.com/u/regularfry)\ **Post date:** [March 22, 2006, 10:23am UTC](https://www.ruby-forum.com/t/feedtools/84839/3 "2006-03-22T10:23:37Z")
eduard wrote: > Is it possible that the feed that you’re trying to open is not > accessible and that’s why it it’s timing out? > It’s not timing out - when it fails, it fails hard and fast (less than a > second after the method call) with a deadlock. It stinks of threads not > behaving themselves, but I don’t know what I can be doing differently to > everyone else if I’m the only one seeing this. An unavailable RSS feed > shouldn’t be able to knock over the Ruby interpreter (and thus the > app)… ---
**Author:** ![regularfry](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@regularfry](https://www.ruby-forum.com/u/regularfry)\ **Post date:** [March 25, 2006, 1:59am UTC](https://www.ruby-forum.com/t/feedtools/84839/4 "2006-03-25T01:59:36Z")
On 2006-03-22 04:21:16 -0500, Alex Y. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) said: > eduard wrote: > > > Is it possible that the feed that you’re trying to open is not > > accessible and that’s why it it’s timing out? > > It’s not timing out - when it fails, it fails hard and fast (less than > > a second after the method call) with a deadlock. It stinks of threads > > not behaving themselves, but I don’t know what I can be doing > > differently to everyone else if I’m the only one seeing this. An > > unavailable RSS feed shouldn’t be able to knock over the Ruby > > interpreter (and thus the app)… Are you using feed caching? I have seen the segfaults before, but not since I started driving the feed cache directly, and only calling Feed.open when there is new stuff. My motivation for doing this is that I wanted more visibility and control over the http request and response (for example, I don’t want to bother parsing a cached version of a feed that returns a 304) , but it’s also made things faster. -Ross > **[RossNotes.com is for sale | HugeDomains](https://www.hugedomains.com/domain_profile.cfm?d=rossnotes.com)** > > Stress free and easy shopping experience. Simple and speedy service. ---
**Author:** ![regularfry](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@regularfry](https://www.ruby-forum.com/u/regularfry)\ **Post date:** [March 26, 2006, 10:21am UTC](https://www.ruby-forum.com/t/feedtools/84839/5 "2006-03-26T10:21:24Z")
Ross Karchner wrote: > Are you using feed caching? > My only reason for using it rather than writing my own parser was to get > the caching 🙂 > I have seen the segfaults before, but not since I started driving the > feed cache directly, and only calling Feed.open when there is new stuff. > Have you got an example of working code I could take a look at, by any > chance? > My motivation for doing this is that I wanted more visibility and > control over the http request and response (for example, I don’t want to > bother parsing a cached version of a feed that returns a 304) , but it’s > also made things faster. > That’s sensible, and also something I’d be wanting to do once I’ve got > the basics up and running.