Mumia W.. wrote:
You can restrict FF to use a limited amount of memory. Although it would blow FF out of the water, you could do a "ulimit -Sv 200000" before starting firefox. Do this in a script.Is there any way, instead of restricting a resource, to have a command executed when a setpoint for a given resource is reached? Say, when FF uses 200M of virtual memory, or over 30% of CPU, a job runs which pops up a warning message. That way you know that a problem exists and can handle it BEFORE it gets to the point where the system is locking up.If FF requires more than 200MB of virtual memory, the O/S will abort it spontaneously. Okay, I admit that that is a brute force way of dealing with the problem, but you'd have to abort FF anyway once it has locked up due to swapping.I might¹ do it this way: #!/bin/sh ulimit -Sv 200000 firefox
-- Marc Shapiro mshapiro_42@yahoo.com