Package: src:gsequencer
Followup-For: Bug #857910
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of thi
severity -1 serious
thanks.
Message-ID: <149069136526.17474.11614453442888250327.reportbug@xenakis.iemnet>
X-Mailer: reportbug 7.1.5
Date: Tue, 28 Mar 2017 10:56:05 +0200
Package: src:gsequencer
Followup-For: Bug #857910
justification:
gsequencer appears to be not-yet releasable.
after a major p
Hi
Note some finalize() methods don't g_object_unref() all struct fields.
It has a strong relation to this bug.
Further GObject::dispose() requires Bug#857930 to be fixed.
Bests,
Joël
On Thu, Mar 16, 2017 at 1:25 PM, Joël Krähemann wrote:
> Hi
>
> Basically the changes from 0.7.122.6 to 0.7.1
Hi
Basically the changes from 0.7.122.6 to 0.7.122.7
I have dedicated this release to memory-leaks.
Note it includes some bug-fixes we should check
if they are applicable to 0.7.122-2
http://download.savannah.gnu.org/releases/gsequencer/stable
Best,
Joël
On Thu, Mar 16, 2017 at 11:53 AM, Tino M
Hi,
please try to provide further details, like the exact upstream version
that contains the necessary change, or maybe a git commit from the
upstream repository that implements this.
Regards,
Tino
Hi
Upstream includes the wished changes. We could do a diff and strip
unwanted changes.
Bests,
Joël
On Thu, Mar 16, 2017 at 11:12 AM, Joël Krähemann wrote:
> Source: gsequencer
> Version: 0.7.122-2
> Severity: important
>
> Dear Maintainer,
>
> GObject::dispose() is not implemented. But it is
Source: gsequencer
Version: 0.7.122-2
Severity: important
Dear Maintainer,
GObject::dispose() is not implemented. But it is necessary in order to release
circular dependencies properly.
It causes to application to leak memory while playback.
Only by program termination it is released.
The appli
7 matches
Mail list logo
