Re: max-cache-size doesn't work with 9.5.0b1

On 04/03/08 19:46, JINMEI Tatuya / 神明達哉 wrote:
Hmm, this is odd in two points:
1. the "X" malloc option doesn't seem to work as expected. I expected
a call to malloc() should trigger an assertion failure (within the
malloc library) at a much earlier stage. Does it change if you try
the alternative debugging approach I mentioned before? That is:
- create a symbolic link from "/etc/malloc.conf" to "X":
# ln -s X /etc/malloc.conf
- start named with a moderate limitation of virtual memory size, e.g.
# /usr/bin/limits -v 384m $path_to_named/named <command line options>

2. Whether it's related to this max-cache-size issue, the assertion
failure in mem.c wasn't an expected result; this is likely to be a
bug anyway. If the process dumped a core, can you show the
stack backtrace of it?
(gdb) thread apply all bt full

No effect, the process grows happily. I don't have a core dump.

This means about 31 log messages per second. This may not be
extremely frequent, but if some memory is lost for every log message,
I guess it could be a reason for the growing memory at the hight rate
we've seen.

What if you change the channel setting from:

I've added this, so now the server doesn't log much (after start, noting):
category default { null; };

The memory usage still grows.

--
Attila Nagy e-mail: Attila.Nagy@xxxxxx
Free Software Network (FSN.HU) phone: +3630 306 6758
http://www.fsn.hu/

_______________________________________________
freebsd-performance@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-performance
To unsubscribe, send any mail to "freebsd-performance-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Determine calling function
    ... responding to the failure by trying again corresponds closely to ... a malloc() failure by tring another malloc, ... memory, not at the actual point of failure. ... address from 0 to 0x7fffffff or so will cause a core dump. ...
    (comp.lang.c)
  • Thank You -- Thomas J. Gritzan
    ... Thomas -- Your suggestion to malloc() out a block of memory was the ... Below are some details of my memory issues ... ... As a work around solution I guessed a ram disk would solve the ... persistence will frustrate the off topic police and give them a target ...
    (comp.lang.c)
  • Re: Simple question about headers and malloc!
    ... Therefore I am making all of its declarations ... memory (using malloc) and then exit back to main. ... allocation, I get data strored from the second allocation... ...
    (microsoft.public.vc.language)
  • Re: ten thousand small processes
    ... Stack needs to be executable for the current signal trampoline ... the use of malloc() that is causing your primary ... if there is any heap memory in use at all, no matter what you do, ... either directly, as a 4M page mapping (not used for user processes, ...
    (freebsd-performance)
  • Re: Review: My C FAQ Page
    ... the definition of memory leak is good but the information on ... this is not the most efficient way to allocate the 2-d array. ... You have ROW+1 calls to malloc. ... Allocate ROW pointers. ...
    (comp.lang.c)