How to free memory after ExtractPageText?

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hello,

I'm using ExtractPageText from a clarion program - all works very well but I don't know how to release the memory taken-up by the returned string. Any clues on this? Wondering if I need to make an api call of some kind involving address of the string.

Thanks,
Simon

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Simon Kemp Members Profile Find Members Posts Beginner Joined: 17 Sep 12 Status: Offline Points: 3	Post Options Post Reply Quote Simon Kemp Report Post Thanks(0) Quote Reply Topic: How to free memory after ExtractPageText? Posted: 17 Sep 12 at 8:55AM
	Hello, I'm using ExtractPageText from a clarion program - all works very well but I don't know how to release the memory taken-up by the returned string. Any clues on this? Wondering if I need to make an api call of some kind involving address of the string. Thanks, Simon

AndrewC Members Profile Find Members Posts Moderator Group Joined: 08 Dec 10 Location: Geelong, Aust Status: Offline Points: 841	Post Options Post Reply Quote AndrewC Report Post Thanks(0) Quote Reply Posted: 17 Sep 12 at 4:10PM
	Calling QP.LibraryVersion() should free that large buffer and return a much smaller buffer of 4 bytes. The DLL always keeps the last string result from the DLL active and the easiest way to free it is to call the DLL again with a function such as LibraryVersion. This method allows us much more flexibility when working with string buffers. Andrew.

Simon Kemp Members Profile Find Members Posts Beginner Joined: 17 Sep 12 Status: Offline Points: 3	Post Options Post Reply Quote Simon Kemp Report Post Thanks(0) Quote Reply Posted: 17 Sep 12 at 4:36PM
	That is making loads of sense. I'll try soonish and report back. Should explain that from clarion I can't actually take a "cstring" (null terminated string) as a return value. The workround is to prototype that QuickPDF is returning a long, then reference that address as a cstring. It left me thinking that housekeeping had to happen from my side - dumb of me. And now realise I have to be careful to finish working with my 'pretend cstring' before asking QuickPDF to do anything else. Thank-you.

Simon Kemp Members Profile Find Members Posts Beginner Joined: 17 Sep 12 Status: Offline Points: 3	Post Options Post Reply Quote Simon Kemp Report Post Thanks(0) Quote Reply Posted: 18 Sep 12 at 6:36AM
	Confirmed that quickpdf is tidying-up correctly. My memory leak must be somewhere else... Thanks for the help, Simon