Operating System - HP-UX
1777284 Members
2261 Online
109066 Solutions
New Discussion

aCC runtime: Uncaught exception of type "bad_alloc"

 
EU-Admins-UNIX
Regular Advisor

aCC runtime: Uncaught exception of type "bad_alloc"

Hi

 

We are trying to startup gpm (glanceplus) on a PA-RISC RP8420 running 11.31.

 

It has 64GB of memory, and the following settings:

 

maxdsiz                         4294963200       4294963200     Immed
maxdsiz_64bit            274877906944  274877906944   Immed
maxfiles                        15000                    15000
maxfiles_lim               15000                    15000          Immed
maxssiz                         70000000            70000000       Immed
maxssiz_64bit            1073741824     1073741824     Immed
maxtsiz                          1073741824     1073741824     Immed
maxtsiz_64bit             8589934592    8589934592     Immed

 

It was shutdown cleanly, but upon startup we got the message in the Subject field.

 

swapinfo shows:

 

             Kb      Kb      Kb   PCT  START/      Kb
TYPE      AVAIL    USED    FREE  USED   LIMIT RESERVE  PRI  NAME
dev     8388608       0 8388608    0%       0       -    1  /dev/vg00/lvol2
dev     8388608       0 8388608    0%       0       -    1  /dev/vg01/swap1
dev     8388608       0 8388608    0%       0       -    1  /dev/vg01/swap2
dev     8388608       0 8388608    0%       0       -    1  /dev/vg01/swap3
dev     8388608       0 8388608    0%       0       -    1  /dev/vg01/swap4
dev     8388608       0 8388608    0%       0       -    1  /dev/vg01/swap5
reserve       - 20545984 -20545984
memory  63900224 26785748 37114476   42%

 

We also have

 

HP-ACC-Link                           C.11.31.03     HP aCC_link Bundle

 

Any ideas?

 

Regards

 

Tariq

 

 

P.S. This thread has been moved from HP-UX > System Administration to HP-UX > languages. - HP Forum Moderator

5 REPLIES 5
Dennis Handly
Acclaimed Contributor

Re: aCC runtime: Uncaught exception of type "bad_alloc"

The message means what it says.  You are out of heap space.

Your maxdsiz and maxdsiz_64bit values seem reasonable.

What does the file command show on gpm?

 

>swapinfo shows:

 

Please provide the "swapinfo -tam" output, at the time of the abort.

EU-Admins-UNIX
Regular Advisor

Re: aCC runtime: Uncaught exception of type "bad_alloc"

Hi Dennis

 

Straight after gpm gave the error, swapinfo -tam shows:

 

             Mb      Mb      Mb   PCT  START/      Mb
TYPE      AVAIL    USED    FREE  USED   LIMIT RESERVE  PRI  NAME
dev        8192       0    8192    0%       0       -    1  /dev/vg00/lvol2
dev        8192       0    8192    0%       0       -    1  /dev/vg01/swap1
dev        8192       0    8192    0%       0       -    1  /dev/vg01/swap2
dev        8192       0    8192    0%       0       -    1  /dev/vg01/swap3
dev        8192       0    8192    0%       0       -    1  /dev/vg01/swap4
dev        8192       0    8192    0%       0       -    1  /dev/vg01/swap5
reserve       -   23008  -23008
memory    62403   26175   36228   42%
total    111555   49183   62372   44%       -       0    -

Dennis Handly
Acclaimed Contributor

Re: aCC runtime: Uncaught exception of type "bad_alloc"

>62,372 MB

 

Looks like plenty of swap.

What does" ulimit -a" show?

EU-Admins-UNIX
Regular Advisor

Re: aCC runtime: Uncaught exception of type "bad_alloc"

time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         4194300
stack(kbytes)        68356
memory(kbytes)       unlimited
coredump(blocks)     4194303
nofiles(descriptors) 15000

Dennis Handly
Acclaimed Contributor

Re: aCC runtime: Uncaught exception of type "bad_alloc"

>data(kbytes)         4194300

 

It looks like that matches maxdsiz, 4 GB.

 

Perhaps running tusc on gpm may tell us something:

tusc -fp -ea -o tusc.out gpm