Brian Candler wrote:
> Just a few thoughts (from someone who doesn't know anything about the
> internal operation of joe):
> - Check the output of 'ulimit -a' to see if you have a limit of, say, 64MB
> per process set.
Looks like it's unlimited, unless I interpret this wrong (?):
$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) 4
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 7168
virtual memory (kbytes, -v) unlimited
> - Monitor the process with 'top' or 'ps' while you are running your macros
> 300 or 400 times in another window. See if the memory usage is going up. See
> what's the highest value it gets to. That might show if there's a memory
> leak in joe.
In top, when I did this and crashed joe, CPU usage only goes up to abour 2%,
while memory usage shows only about 0.0% - 0.1%. In general, only CPU usage
went up, and then joe crashed. This machine is not so busy also, ie. when I
tried this, the machine was mostly idle and very little IO activity.
Joe crashed with the following message in console: "vfile: out of memory"
> - Do you get a core dump? If so, gdb might be able to interpret it usefully.
There's no Core dump.
Thanks for the suggestions.
Reuben D. Budiardja