[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem |
Date: |
Mon, 14 Jan 2019 11:48:28 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
Update of bug #55287 (project octave):
Release: 5.0.0 => 5.0.1
_______________________________________________________
Follow-up Comment #51:
@Pantxo: Seems like your text in comment #49 got clipped.
I do agree that ASAN isn't very helpful here since the memory is freed on exit
from Octave. We need intermediate memory reporting, for which I have been
using top, but any tool, including the patch attached to this report, should
work for that. 'top' is easier for me because it is built-in to the OS, and
as I go backwards as far as 3 years ago in the code base it becomes hard to
compile add-ins like the memory tool.
I think there are at least two bugs here which is why we are getting different
behavior when the action is plot() versus set(). Rather than decide on the
definitive test, I would just choose which test you want to debug first and
mention it when you present results.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55287>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, (continued)
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/09
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Robert F, 2019/01/09
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/09
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/09
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Doug Stewart, 2019/01/09
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/10
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/11
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/11
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/14
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/14
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem,
Rik <=
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/14
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/14
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/15
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/15
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Philip Nienhuis, 2019/01/17
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/17
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Robert F, 2019/01/17
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/18
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/18
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, John W. Eaton, 2019/01/18