|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output |
Date: | Mon, 17 Jan 2022 00:42:48 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 |
Follow-up Comment #8, bug #61813 (project octave): I bisected on the default branch and not surprisingly, it is this change that appears to be causing the trouble: # User John W. Eaton <jwe@octave.org> # Date 1633116351 14400 # Fri Oct 01 15:25:51 2021 -0400 # Node ID b00ff462e0f291bca599b4c8607080a001075dc9 # Parent f3ffb4596bd86d583358129735bff443b9b4b6d8 improve efficiency of mxArray -> octave_value conversion I haven't had a chance to determine what I did wrong but will look at this before the 7.1.0 release. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?61813> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |