- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Memory Leak in /lib/libCsup.2
Operating System - HP-UX
1753427
Members
4947
Online
108793
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2006 04:02 AM
тАО09-11-2006 04:02 AM
Memory Leak in /lib/libCsup.2
We have noticed memory leak occuring in one of our Application Servers. Majorly the leaks are occuring in two shared libraries, firstly oracle specific shared library libclntsh.sl.9.0 and secondly in /lib/libCsup.2. Attached is the WDB 5.3 memory leak report.
We are not able to ascertain the cause of these leaks at our code level. It would be helpful to have the following info.
1. If this is a known problem?
2. If this is indeed a known problem, then do we have some patch for this?
3. Are any workarounds available for this problem?
4. Do we have any references to a similar problem occured in the past?
Environment:
HP-UX 11.11, aCC version A.03.60, RogueWave Library 7.3
*********************************
We are not able to ascertain the cause of these leaks at our code level. It would be helpful to have the following info.
1. If this is a known problem?
2. If this is indeed a known problem, then do we have some patch for this?
3. Are any workarounds available for this problem?
4. Do we have any references to a similar problem occured in the past?
Environment:
HP-UX 11.11, aCC version A.03.60, RogueWave Library 7.3
*********************************
- Tags:
- leak
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2006 04:10 AM
тАО09-11-2006 04:10 AM
Re: Memory Leak in /lib/libCsup.2
Shalom,
Normally memory leaks have more to do with bad application programmer code than with the libraries themselves.
I do recommend having your system to the June 2006 bi-annual patch set and having the most current aCC version installed that is compatible with your RogueWave Library.
SEP
Normally memory leaks have more to do with bad application programmer code than with the libraries themselves.
I do recommend having your system to the June 2006 bi-annual patch set and having the most current aCC version installed that is compatible with your RogueWave Library.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2006 08:59 AM
тАО09-13-2006 08:59 AM
Re: Memory Leak in /lib/libCsup.2
Hi,
you can't figure out where the leaks come from because the stack height is not big enough to hold it full
You should rerun your gdb session with
set heap-check frame-count 32
(32 should be enough;-)
Then please repost your new report.
++Cyrille
you can't figure out where the leaks come from because the stack height is not big enough to hold it full
You should rerun your gdb session with
set heap-check frame-count 32
(32 should be enough;-)
Then please repost your new report.
++Cyrille
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2006 07:01 PM
тАО09-20-2006 07:01 PM
Re: Memory Leak in /lib/libCsup.2
you are looking at the topmost (#0) frame of the stack trace in each leak. this is not the best way to look at the leak trace.
you will see that in each case where the top frame is in libCsup.2, the bottom most frame is in liborb.sl.
gdb is reporting where malloc got called. as you would expect, the libCup.2 new operator implementation calls malloc. the real problem is with whoever is calling new so many times and not calling delete (directly or indirectly).
this is why cyrille is asking you to increase the stack frame count.
--
ranga
[i work for hpe]
you will see that in each case where the top frame is in libCsup.2, the bottom most frame is in liborb.sl.
gdb is reporting where malloc got called. as you would expect, the libCup.2 new operator implementation calls malloc. the real problem is with whoever is calling new so many times and not calling delete (directly or indirectly).
this is why cyrille is asking you to increase the stack frame count.
--
ranga
[i work for hpe]
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP