# Memory error **URL:** \ **Category:** Rails\ **Created:** [August 17, 2006, 5:35pm UTC](https://www.ruby-forum.com/t/memory-error/65349 "2006-08-17T17:35:39Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ratcheer](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/aca169/32.png) [@ratcheer](https://www.ruby-forum.com/u/ratcheer)\ **Post date:** [August 17, 2006, 5:35pm UTC](https://www.ruby-forum.com/t/memory-error/65349/1 "2006-08-17T17:35:39Z")
I’m using ruby on rails on a Macbook Pro with sqlite3. I’m finding that memory for the ruby process stays about 20mb until I hit an error after which the mermory doesn’t seem to be released and keeps going up until I can’t use my machine. What could be causing this? is it using sqlite3? have I set up rails or ruby wrong? Tim ---
**Author:** ![ratcheer](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/aca169/32.png) [@ratcheer](https://www.ruby-forum.com/u/ratcheer)\ **Post date:** [August 17, 2006, 5:53pm UTC](https://www.ruby-forum.com/t/memory-error/65349/2 "2006-08-17T17:53:43Z")
On 8/17/06, Tim C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I’m using ruby on rails on a Macbook Pro with sqlite3. I’m finding that > memory for the ruby process stays about 20mb until I hit an error after > which the mermory doesn’t seem to be released and keeps going up until I > can’t use my machine. > > What could be causing this? is it using sqlite3? have I set up rails or ruby > wrong? Reports of memory leaks have started popping up on the mongrel mailing list. Now, the current thought is that it has nothing to do with mongrel, and most likely a bug in Rails 1.1.6. It might be helpful, whether you’re using mongrel or not, to post details about your server and what mode (development, production) you’re running in. – James ---
**Author:** ![ratcheer](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/aca169/32.png) [@ratcheer](https://www.ruby-forum.com/u/ratcheer)\ **Post date:** [August 17, 2006, 6:29pm UTC](https://www.ruby-forum.com/t/memory-error/65349/3 "2006-08-17T18:29:46Z")
I’m not using mongrel I’m using webrick. My collegue uses the same code base on a windows machine with webrick and doesn’t seem to get the same memory isseues. ---
**Author:** ![ratcheer](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/aca169/32.png) [@ratcheer](https://www.ruby-forum.com/u/ratcheer)\ **Post date:** [August 17, 2006, 10:33pm UTC](https://www.ruby-forum.com/t/memory-error/65349/4 "2006-08-17T22:33:21Z")
On Thu, 2006-08-17 at 10:51 -0500, James L. wrote: > list. Now, the current thought is that it has nothing to do with > mongrel, and most likely a bug in Rails 1.1.6. It might be helpful, > whether you’re using mongrel or not, to post details about your server > and what mode (development, production) you’re running in. The only report I’ve seen is from Carl L. so if you know of more please point me at the references. I’m also cooking up a slightly better memory debugger for mongrel in the next pre-release. It’s helped a few people find memory leaks in their rails code. – Zed A. Shaw > **[Zed A. shaw](https://zedshaw.com/)** > > Personal essays and writings by Zed A. Shaw. [http://mongrel.rubyforge.org/](http://mongrel.rubyforge.org/) [http://www.railsmachine.com/](http://www.railsmachine.com/) – Need Mongrel support? ---
**Author:** ![ratcheer](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/aca169/32.png) [@ratcheer](https://www.ruby-forum.com/u/ratcheer)\ **Post date:** [August 17, 2006, 10:46pm UTC](https://www.ruby-forum.com/t/memory-error/65349/5 "2006-08-17T22:46:13Z")
Zed S. wrote: > I’m also cooking up a slightly better memory debugger for mongrel in the > next pre-release. It’s helped a few people find memory leaks in their > rails code. Hey Zed, What else do you have planned for future versions of Mongrel? Joe ---
**Author:** ![ratcheer](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/aca169/32.png) [@ratcheer](https://www.ruby-forum.com/u/ratcheer)\ **Post date:** [August 18, 2006, 5:14pm UTC](https://www.ruby-forum.com/t/memory-error/65349/6 "2006-08-18T17:14:47Z")
On 8/17/06, Zed S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > Reports of memory leaks have started popping up on the mongrel mailing > > rails code. > > I was mistaken. I swear that I saw more than one report, but when I > > went back and checked it was both of Carl’s threads. My bad. – James ---
**Author:** ![ratcheer](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/aca169/32.png) [@ratcheer](https://www.ruby-forum.com/u/ratcheer)\ **Post date:** [August 18, 2006, 10:12pm UTC](https://www.ruby-forum.com/t/memory-error/65349/7 "2006-08-18T22:12:24Z")
On Fri, 2006-08-18 at 10:13 -0500, James L. wrote: > On 8/17/06, Zed S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > > > Reports of memory leaks have started popping up on the mongrel mailing > > > list. Now, the current thought is that it has nothing to do with > > > mongrel, and most likely a bug in Rails 1.1.6. It might be helpful, > > > whether you’re using mongrel or not, to post details about your server > > > and what mode (development, production) you’re running in. > > > > The only report I’ve seen is from Carl L. so if you know of more > > please point me at the references. > I was mistaken. I swear that I saw more than one report, but when I > went back and checked it was both of Carl’s threads. My bad. Sheesh James, that’s how FUD starts. Next week will be the big post on how “Mongrel leaks like crazy, time to switch to …” 🙂 If you run into memory leak problems though, let me know. – Zed A. Shaw > **[Zed A. shaw](https://zedshaw.com/)** > > Personal essays and writings by Zed A. Shaw. [http://mongrel.rubyforge.org/](http://mongrel.rubyforge.org/) [http://www.railsmachine.com/](http://www.railsmachine.com/) – Need Mongrel support?