Re: memory leak doing gsk_environment_open()

Good to know. I like the default behavior, but good to know. Thanks, Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carl Kugler Sent: Thursday, February 04, 2016 11:54 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: memory leak

Re: memory leak doing gsk_environment_open()

. Is the extra effort/processing worth the saving of the Heap storage while not in use? At 11:43 -0800 on 02/04/2016, Charles Mills wrote about Re: memory leak doing gsk_environment_open(): OK, I ran some tests. The bad news is yes, in my environment, GSK seems to leak storage

Re: memory leak doing gsk_environment_open()

That was an awesome suggestion! I am having a great time going through my code and finding a couple of leaks. I do note that I have several leaks on setlocale(). It's only 828 bytes but since I call it once per thread it might add up. I have another leak on dllinit() for 155CC0 bytes Does

Re: memory leak doing gsk_environment_open()

On Behalf Of Charles Mills Sent: Tuesday, February 02, 2016 4:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: memory leak doing gsk_environment_open() I use the gsk functions from C++ with no (known!) issues. I will look at the code when I get back to the offic

Re: memory leak doing gsk_environment_open()

I am curious if running GSKSVR to take care of cert cache helps. On Thu, Feb 4, 2016, 2:54 PM Carl Kugler wrote: > > if the requested storage that caused the heap to expand gets returned > with a free() or delete I do not believe the C runtime issues a STORAGE > >

Re: memory leak doing gsk_environment_open()

> if the requested storage that caused the heap to expand gets returned with a > free() or delete I do not believe the C runtime issues a STORAGE > RELEASE for the additional increment of heap: it keeps it around in > anticipation of future malloc() or new requests. It does not RELEASE the >

Re: memory leak doing gsk_environment_open()

ram that was sharing the address space. HTH Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Janet Graff Sent: Tuesday, February 02, 2016 2:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: memory leak doing gsk_environment_open() I hav

memory leak doing gsk_environment_open()

I have a long running STC that does an HTTP sequence using secure sockets. I can monitor the memory usage throughout my calls. I note that my above the line storage shows a 1M increase after the gsk_environement_open(). That memory is not freed after the gsk_environment_shutdown(),

Re: memory leak doing gsk_environment_open()

I have run RPTSTG on the application several times in the past and tuned things. I can do this again. However I can see this leak every time I run through an HTTP creation of socket, request, and socket termination. Which is what makes me believe that either the memory isn't cleaned up or

Re: memory leak doing gsk_environment_open()

al Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Janet Graff Sent: Tuesday, February 02, 2016 5:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: memory leak doing gsk_environment_open() I have a long running STC that does an HTTP sequence using secure socket

Re: memory leak doing gsk_environment_open()

Try the following runtime option HEAPCHK(ON,1,0,10,10). It will produce a dump with a trace of all memory allocations that have no free. However, it's not unusual for APIs to allocate memory once and store the pointer in WSA, kind of like a singleton. That's how the standard stream libraries

Re: memory leak doing gsk_environment_open()

te: 02/02/2016 3:33 PM (GMT-08:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: memory leak doing gsk_environment_open() I have run RPTSTG on the application several times in the past and tuned things.   I can do this again.  However I can see this leak every time I run through an HTTP cr