Sporadically my systems stops cupsd and refuses to start new programs like yum or Seamonkey. Seems my system runs out of some ressources which needs a reboot to cure. As I constatly watch memory usage with above512 I don't think memory runs out neither lower nor higher SM.
Heavy usage of Seamonkey editing wiki sites which seem to use a lot of javascript code seems to trigger this behaviour.
Here the output of cupsd when it stopped working after a few hours, stderr out from Seamonkey running a few hours until it utilized both cores up to 100% and I closed. Including to restart SM afterward failed. And a failing 'yum list libc*'.
As said I think this is triggered by either resource hungry javascripts or the flaky JS code in SM. But any chance to circumvent such problems? Should I try .exp repository or is it clear from this logs that SM (JS) is the problem and nothing can't be done against?
I need this system for day time work so I can only test things when chances are high that things don't get worse. F.i. newer SM builds I tested a while ago crashes way to often to be useful for me. Any hints?
Sporadically my systems stops cupsd and refuses to start new programs like yum or Seamonkey. Seems my system runs out of some ressources which needs a reboot to cure. As I constatly watch memory usage with above512 I don't think memory runs out neither lower nor higher SM.
Heavy usage of Seamonkey editing wiki sites which seem to use a lot of javascript code seems to trigger this behaviour.
Here the output of cupsd when it stopped working after a few hours, stderr out from Seamonkey running a few hours until it utilized both cores up to 100% and I closed. Including to restart SM afterward failed. And a failing 'yum list libc*'.
As said I think this is triggered by either resource hungry javascripts or the flaky JS code in SM. But any chance to circumvent such problems? Should I try .exp repository or is it clear from this logs that SM (JS) is the problem and nothing can't be done against?
I need this system for day time work so I can only test things when chances are high that things don't get worse. F.i. newer SM builds I tested a while ago crashes way to often to be useful for me. Any hints?