All is well that ends.......

well ?
To find out cause of resource hog - the usual method is to run
top
&/or
ps ax
Then the user may use (see "man" pages for all)
Kill -9
plus the process I.D. number found from using either utility ("top or ps ax")
FWIW (

Hi Joe) there should be little discernible Performance Variation to any
Journalled F/Sys - beit reiser/ext3/xfs, etc.
Robustness may be more due to what caused any file corruption:
Such as hot-key Ctrl+Alt+ Bkspc on running desktop
WHILE apps are still open.
Both reiser & ext3 have own repair tools
Reiser4 is (arguably) superior - but at a trade-off of benefits.
The jury is still out on that.
In end NO "blanket assertions" may be correctly stated >
All seems to vary by user-tasking contemplated
O.T ~ Much the same applies to: latency/newer queuing-scheduler & WHY any desktop user
would NEED real-time mode (save for E.G. music-synthesizing) ?
More Ram is alway a good thing - but cannot compensate for slower
CPU architecture - nor faster bus I/out & drive devices !
The first gives more buffering cache
The latter faster CPU cycles (most is wasted anyway as top shows.
Huge data transfer needs optimal in/out
Lengthy complicated compiles need CPU power (for those w/more than one box - use distcc)