From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Samuel CHEMLA <chemla.samuel@gmail.com>
Cc: Gregor Jasny <gjasny@googlemail.com>, Sean Young <sean@mess.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>
Subject: Re: [Bug report] dvbv5-zap crash dvb-tool ARMHF builds
Date: Mon, 25 Mar 2019 14:08:38 -0300 [thread overview]
Message-ID: <20190325140838.71f88eac@coco.lan> (raw)
In-Reply-To: <CANJnhGfRtEwAony5Z4rFMPcu58aF2k0G+9NSkMKsq_PhfmSNqw@mail.gmail.com>
Em Mon, 25 Mar 2019 17:33:30 +0100
Samuel CHEMLA <chemla.samuel@gmail.com> escreveu:
> Hi guys,
>
> I'm afraid I'm coming with sad news.
> I just tried both stable-1.12 and stable-1.16 on a raspberry pi 2, and
> random hangs are back (see https://bugs.launchpad.net/raspbian/+bug/1819650
> ).
> I previously test both branches on a raspberry zero and issues were gone
> (same raspbian version).
> There may be more memory issues somewhere...
Could you test it with valgrind?
>
> Sam
>
> Le jeu. 21 mars 2019 à 20:59, Gregor Jasny <gjasny@googlemail.com> a écrit :
>
> > Hello,
> >
> > On 21.03.19 12:30, Mauro Carvalho Chehab wrote:
> > > I went ahead and cherry-picked the relevant patches to -1.12, -1.14 and
> > > -1.16, and tested both dvbv5-zap and dvbv5-scan with all versions. So,
> > we can
> > > release a new minor version for all those stable branches.
> > >
> > > After the patches, on my tests, I didn't get any memory leaks or
> > > double-free issues.
> >
> > I issues a new 1.12, 1.14, and 1.16 release.
> >
> > Thanks,
> > Gregor
> >
> >
Thanks,
Mauro
next prev parent reply other threads:[~2019-03-25 17:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f4b69417-06c3-f9ab-2973-ae23d76088b8@gmail.com>
[not found] ` <29bad771-843c-1dee-906c-6e9475aed7d8@gmail.com>
2019-03-12 15:07 ` [Bug report] dvbv5-zap crash dvb-tool ARMHF builds Gregor Jasny
2019-03-15 22:34 ` Sean Young
2019-03-17 9:52 ` Mauro Carvalho Chehab
2019-03-19 19:45 ` Mauro Carvalho Chehab
2019-03-20 19:38 ` Gregor Jasny
2019-03-21 9:41 ` Sean Young
2019-03-21 11:30 ` Mauro Carvalho Chehab
2019-03-21 19:59 ` Gregor Jasny
[not found] ` <CANJnhGfRtEwAony5Z4rFMPcu58aF2k0G+9NSkMKsq_PhfmSNqw@mail.gmail.com>
2019-03-25 17:08 ` Mauro Carvalho Chehab [this message]
2019-03-26 7:35 ` Samuel CHEMLA
2019-03-26 13:26 ` Sean Young
2019-03-26 15:10 ` Samuel CHEMLA
2019-03-26 15:31 ` Mauro Carvalho Chehab
2019-03-28 18:48 ` Samuel CHEMLA
2019-03-28 19:17 ` Mauro Carvalho Chehab
2019-03-28 19:48 ` Gregor Jasny
2019-03-28 20:04 ` Mauro Carvalho Chehab
2019-04-01 18:58 ` Samuel CHEMLA
2019-04-08 6:32 ` Samuel CHEMLA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190325140838.71f88eac@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=chemla.samuel@gmail.com \
--cc=gjasny@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=sean@mess.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox