[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #61813] memory management bug when calling MEX
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output |
Date: |
Mon, 28 Feb 2022 14:09:09 -0500 (EST) |
Follow-up Comment #17, bug #61813 (project octave):
I pushed a set of changes to allow Sparse<T> to accept allocators and then to
use a custom allocator/memory resource when transferring data from sparse
mxArray objects to octave_value objects, same as we do for Array<T> now.
http://hg.savannah.gnu.org/hgweb/octave/rev/b1301358b040
http://hg.savannah.gnu.org/hgweb/octave/rev/4fc0b7269803
The custom allocator is only enabled if std::pmr::polymorphic_allocator is
available and OCTAVE_HAVE_STD_PMR_POLYMORPHIC_ALLOCATOR is defined. Could you
update and verify that this change also avoids the crash?
Also, can you let me know whether OCTAVE_HAVE_STD_PMR_POLYMORPHIC_ALLOCATOR is
defined in your builds?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61813>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output, John W. Eaton, 2022/02/20
- [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output, Sébastien Villemot, 2022/02/21
- [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output, John W. Eaton, 2022/02/21
- [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output, Sébastien Villemot, 2022/02/22
- [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output, Markus Mützel, 2022/02/22
- [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output, Sébastien Villemot, 2022/02/23
- [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output, John W. Eaton, 2022/02/23
- [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output, Sébastien Villemot, 2022/02/23
- [Octave-bug-tracker] [bug #61813] memory management bug when calling MEX that returns an output,
John W. Eaton <=