1748185 Members
4223 Online
108759 Solutions
New Discussion юеВ

Growing process memory

 
Dennis Handly
Acclaimed Contributor

Re: Growing process memory

>1 9357656 106337 0x411e3440 __libc_mutex_alloc()

These means you still need to recompile some libs with -D__HPACC_FIXED_REFCNT_MUTEX. There are ~106 K strings.


(gdb) info heap 0
290869526 bytes in 3870584 blocks (92.49% of all bytes allocated)
These range in size from 4 to 34812 bytes and are allocated

>How I verify this memory?

Well without a function or stack trace, I'm not sure what it is trying to tell you??

That size is maybe that 400 Mb you initially mentioned.

What version of wdb do you have?
Benedetto Mangiapane
Frequent Advisor

Re: Growing process memory

Ok I must recompile all libs.

The version of wdb is:
HP WDB-GUI - HP Debugger Graphical User Interface - Version 5.4
Rev: 20060320.192245

Infact, the function is unknown "???()", I ask to you if it is possible to understand in other way?
Dennis Handly
Acclaimed Contributor

Re: Growing process memory

>Ok I must recompile all libs.

No, you don't have to do that. But if you want to get the reduced memory and 5 to 10% speed up, you should do it.

> HP WDB-GUI - HP Debugger Graphical User Interface - Version 5.4

You may want to download a newer gdb.

>the function is unknown "???()", I ask to you if it is possible to understand in other way?

I didn't see any stack trace when you did:
(gdb) info heap 0

Did you snip it, or is this a symptom of why things are messed up?

I hope you haven't stripped your executable??
But I would have thought there would be more of them if that was true.
Benedetto Mangiapane
Frequent Advisor

Re: Growing process memory

Hi,
I call chatr command to the process, and it show me:

...
global hash table disabled
plabel caching disabled
global hash array size:1103
global hash array nbuckets:3
shared vtable support disabled
static branch prediction disabled
executable from stack: D (default)
kernel assisted branch prediction enabled
lazy swap allocation disabled
text segment locking disabled
data segment locking disabled
third quadrant private data space disabled
fourth quadrant private data space disabled
third quadrant global data space disabled
data page size: D (default)
instruction page size: D (default)
nulptr references disabled
shared library private mapping disabled
shared library text merging disabled

Someone of these its not correct?
Not still I resolved the problem...
Dennis Handly
Acclaimed Contributor

Re: Growing process memory

>I call chatr command to the process, and it show me:

Why did you use chatr(1)?

>Someone of these its not correct?

Nothing obviously wrong.
Benedetto Mangiapane
Frequent Advisor

Re: Growing process memory

Excuse me,
what should I use?

Thanks.
Dennis Handly
Acclaimed Contributor

Re: Growing process memory

>what should I use?

I was asking why you decided to post the chatr output. I don't remember asking for it. And chatr doesn't tell you if things are stripped. You can use file(1) for that.