I've fixed the leak in the process module; thanks for the report.

There are still 32 bytes leaked by Zorba itself for the dlopen() handle.
I *believe* this is intentional, and that we do not "correctly" close
dlopen()'d libs on purpose to support libjvm-based modules - the JVM
does not respond at all well if it is started more than once in a single
process. Those 32 bytes should be leaked once per module used in the
Zorba process, so it does not amount to much (there are only a few dozen
modules that could possibly be opened, so the max leakage is less than

You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.

  process:exec memory leak

Status in Zorba - The XQuery Processor:
  In Progress

Bug description:
  Running the following query with valgrind will show some memory leak

  import module namespace process="http://www.zorba-xquery.com/modules/process";;

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~zorba-coders
Post to     : zorba-coders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zorba-coders
More help   : https://help.launchpad.net/ListHelp

Reply via email to