From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: purchase@utopiacontrol.com
Cc: linux-media@vger.kernel.org
Subject: Re: Fw: Memory acquisition problem with yavta and media control.
Date: Sat, 31 Aug 2013 22:29:34 +0200 [thread overview]
Message-ID: <1475404.9MHgQaVtRD@avalon> (raw)
In-Reply-To: <F74E216C170F4219AAD7D7D3D5CDFF61@store>
Hi Nilesh,
On Saturday 31 August 2013 10:07:14 purchase@utopiacontrol.com wrote:
> //=================================
> linux-media@vger.kernel.org
> laurent.pinchart@ideasonboard.com
> //=================================
>
> Hi laurent pinchart,
Just Laurent will do :-)
> You have done a great work for snapshot mode image sensor driver for linux.
> I am using your media control tool with yavta test application for
> interfacing the mt9v032 image sensor with Gumstix Overo Water Com board. I
> have successfully tested the snapshot mode with this combination. But the
> problem is that, when I attempt to grab lots of images (thousands) of images
> by this test application yavta. I found that the free memory goes increasing
> by some amount which will not get free. Afterwards I have calculate the
> amount of ram acquires on every snap is about 0.618 KB (after averaging
> 100000 frames). Will you please Give me any reason why this is happening
> with this test application? And how can I get overcome on this problem.
That's definitely not expected and should be debugged. First of all, is the
memory released when you stop yavta ? If it isn't then we have a kernel bug,
if it is the bug could be either on the kernel side or the application side.
--
Regards,
Laurent Pinchart
parent reply other threads:[~2013-08-31 20:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <F74E216C170F4219AAD7D7D3D5CDFF61@store>]
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=1475404.9MHgQaVtRD@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=purchase@utopiacontrol.com \
/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