topic Re: LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow in Operating System - OpenVMS

LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow

Patricia Morman — Wed, 16 Dec 2009 15:42:14 GMT

I have found that calls to LIB$INIT_DATE_TIME_CONTEXT in an external function causes a process to grow continually until I get the message "Maximum Memory Exceeded." I'm using BASIC. Making the calls in the main program is fine, but in an external function the process grows and grows. I'm in the middle of a big project and this has me dead in the water. Any help would be appreciated. Thanks!

Re: LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow

Hoff — Wed, 16 Dec 2009 15:49:12 GMT

Guess: You're probably missing a corresponding call to the LIB$FREE_DATE_TIME_CONTEXT routine to free the context. Calls that are not paired will leak memory.

Re: LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow

Patricia Morman — Wed, 16 Dec 2009 15:56:17 GMT

Good Guess! That did the trick. Thanks so much!!

Re: LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow

Steven Schweda — Wed, 16 Dec 2009 15:57:35 GMT

I know nothing, but I see

http://h71000.www7.hp.com/doc/82final/5932/5932pro_029.html

where it says:

Condition Values Returned
[...]
Any condition value returned by LIB$GET_VM or LIB$ANALYZE_SDESC.

and LIB$GET_VM suggests to me that it's
allocating some VM. Perhaps you need to be
freeing something somewhere. (I don't see
what, however.) Or not calling this thing
repeatedly?

Re: LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow

Patricia Morman — Wed, 16 Dec 2009 16:02:52 GMT

If thou call LIB$INIT_DATE_TIME_CONTEXT thou shalt also call LIB$FREE_DATE_TIME_CONTEXT. You saved my bacon. Thanks!

Re: LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow

Steven Schweda — Wed, 16 Dec 2009 16:27:54 GMT

Note that on that same Web page, the
explanation of LIB$INIT_TIMER mentions
LIB$FREE_TIMER ("You need to call
LIB$FREE_TIMER [...]), but you don't get any
corresponding help with
LIB$INIT_DATE_TIME_CONTEXT.

I assume that it would be a waste of time and
effort, but one could try reporting this to
the VMS documentation people.

Re: LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow

Patricia Morman — Wed, 16 Dec 2009 16:31:14 GMT

Yes, I had looked up the INIT command specifically because I wondered if I had to explicitly release the memory and it mentionned nothing about the FREE conterpart.

Re: LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow

Jon Pinkley — Wed, 16 Dec 2009 18:20:40 GMT

It is hard to tell if reporting documentation errors is worth while or not.

I sent a report to openvmsdoc@hp.com on Dec 3, 2009 concerning incorrect information in the system manager's manual.

The mail did not bounce, but I never got any acknowledgment that anyone had received the mail.

It is definitely a dis-incentive to spending the time to report errors whent there is absolutely no feedback.

Ideally there should be an online errata for manuals, and the online PDF and html should be updated (with a revision number) so the online manuals are always as accurate as possible. They should keep the base level (what was "shipped") and the latest revision onlline.

I still remember replacing pages in the 3 ring binders when a point release came out for the Blue Wall and Orange Wall editions. I am not sure if they issued replacement pages for the Gray Wall edition or not.

Re: LIB$INIT_DATE_TIME_CONTEXT in External Function causes Process to Continually Grow

Jon Pinkley — Sat, 19 Dec 2009 00:47:15 GMT

Well it does appear that someone from HP is reading either this thread or the mail sent to openvmsdoc@hp.com, because I did get a response back on Dec 18th, concerning the mail I sent on Dec 3rd.

So it is worth reporting documentation errors.

Jon