On 3/15/24 13:25, Pierre-Louis Dourneau wrote:
> [You don't often get email from pl.dourn...@klervi.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> On
On 3/12/24, Pierre-Louis Dourneau wrote:
> On 3/8/24, ludovic.desroc...@microchip.com
> wrote:
> > This patch fixes the memory leak but introduces a crash on my side when
> > exiting a graphics app using the Microchip graphics library.
>
> We've tried to reproduce your crash with
Hey Ludovic,
On 3/8/24, ludovic.desroc...@microchip.com
wrote:
> On 3/6/24 20:49, Pierre-Louis Dourneau wrote:
> >
> > From: Arnaud Lahache
> >
> > Fixes a memory leak occurring on each modeset update.
> >
> > Running a program such as libdrm's modetest[0] with this driver exhausts
> > all
On 3/6/24 20:49, Pierre-Louis Dourneau wrote:
>
> From: Arnaud Lahache
>
> Fixes a memory leak occurring on each modeset update.
>
> Running a program such as libdrm's modetest[0] with this driver exhausts
> all available memory after a few minutes. Enabling kmemleak yields a series
> of such
From: Arnaud Lahache
Fixes a memory leak occurring on each modeset update.
Running a program such as libdrm's modetest[0] with this driver exhausts
all available memory after a few minutes. Enabling kmemleak yields a series
of such leak reports:
unreferenced object 0xc21acf40 (size 64):
comm
