If the extra heap size is minor and one-time (being reused when
needed) I would say to just let it stay allocated. Using the setting
to free it after use might be a bad idea since the next time you need
it you will go through another allocate cycle again followed by
another release one. 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 --
that is, it allocates storage that it does not free. The good news
is that (1) it seems to be "one time," not per session; and (2) the
storage is modest: eight allocations totaling 0x510 bytes.
I see an increase in HEAP (the heap specifically named HEAP) with
GSK as opposed to plain old TCP, but it is not dramatic -- nowhere
near a megabyte -- somewhere around 100K.
HTH
Charles
-----Original Message-----
From: IBM Mainframe Discussion List
[mailto:[email protected]] On Behalf Of Charles Mills
Sent: Tuesday, February 02, 2016 4:44 PM
To: [email protected]
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 office Thursday.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
