** Changed in: zorba
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/1027142
Title:
process:exec memory leak
Status in Zorba - The XQuery Processor:
** Branch linked: lp:~zorba-coders/zorba/bug-1027142-process-leak
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/1027142
Title:
process:exec memory leak
Status in Zorba - The XQuery Processor:
** Changed in: zorba
Status: New = In Progress
** Changed in: zorba
Assignee: (unassigned) = Chris Hillery (ceejatec)
** Changed in: zorba
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for
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
4 matches
Mail list logo