|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #56637] Access of a nested structure -> memory leak in mex function |
Date: | Wed, 17 Jul 2019 13:21:09 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36 |
Follow-up Comment #8, bug #56637 (project octave): In other words, we have a minimal example that doesn't show a memory leak. You have a complex example that does show a memory leak. At the moment, it seems most likely that the memory leak is in your code and not in Octave itself. As the reporter, we hope that you will put in some more effort to reduce your complex example to show a complete but minimal example that demonstrates the leak. Or perhaps by attempting to do so you will discover the source of the leak yourself. You might also try running your code under leak detection tools like LeakSanitizer or Valgrind. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?56637> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |