Problem with r1349

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hej!

I updated to r1439 yesterday (from r1348) and I (again) had problems
with the stability of the fcgi process. It seems like there are memory
issues again. What were the changes in r1439? Does it consume much
more memory than r1348? Once the svn repository is available again,
I’ll try some tests and see what I have to do to kill the process.

Urban


http://bettong.net | Urban’s Blog
http://computer-go.bettong.net | Planet Computer-Go

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFFtJvbggNuVCIrEyURAgFBAJ9w23ObRnKKX57LKRXmzJZWYyxOFgCcDNWQ
X6FNRdDpQK3cY4MKutgZ9Tk=
=5euu
-----END PGP SIGNATURE-----


Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jan 23, 2007, at 19:30 , Kevin B. wrote:

Memory issues meaning RPVT growing unchecked?

Sorry, what’s RPVT?

Where are you being hosted? If you’re on TextDrive then yeah, there
seems to be an odd problem with their servers that causes typo to
use roughly twice as much RAM as is usual, at which point TextDrive
automatically kills the dispatch.fcgi process.

Yes, this is hosted on TextDrive. But it’s not getting killed but it
seems like it fails to allocate memory. On the console I started it I
get “[FATAL] failed to allocate memory”.

Urban


http://bettong.net | Urban’s Blog
http://computer-go.bettong.net | Planet Computer-Go

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFFtmzwggNuVCIrEyURAkgRAKCKlQOPY/vL2tvG0ES1dWWrjoq4YQCbBraR
5Tyzzdo9n85ZjHisi5GWoe0=
=+CQn
-----END PGP SIGNATURE-----


Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs