50% is not a tiny little amount :-) but I hear what you say, I just wanted to be sure I am not sitting on something that needs investigation.
What can I do to to help go after the rexximage hangs? Maybe it is not so critical (a reboot fixes it) unless such a build is somehow incomplete? Unfortunately there is no working version of Valgrind available for macOS Mojave yet so I will need to recreate the behavior on High Sierra. Given the number of times I am building it is bound to happen any day now. Hälsningar/Regards/Grüsse, P.O. Jonsson [email protected] > Am 03.01.2019 um 22:05 schrieb Erich Steinböck <[email protected]>: > > Hi P.O., except for the rexximage hangs, the behaviour you report seems to be > perfectly valid. > > Each test run creates a new rexx process, which uses quite some memory, and > then ends. > rxapi is being used by those tests and increases its memory footprint by a > tiny little amount. > rxapi is never supposed to end. > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
