Is it a slight memory leak in Crystal Driver

28 views
Skip to first unread message

valpa

unread,
May 4, 2011, 4:11:53 AM5/4/11
to crystalhd-development
Hi

I use mplayer -slave -idle mode to playe movie all days long. When a
movie finished, it will automatically load another movie without
existing mplayer program.

I then monitor the memory usage in /proc/xxx/status : VmSize, it shows
the memory usage will slightly increase per minutes. after several
days. My 1G ram used up.

I don't know how to give further information. If need, pls tell me.

Thanks,
valpa

Naren (Narendra) Sankar

unread,
May 5, 2011, 12:14:36 PM5/5/11
to crystalhd-...@googlegroups.com
Valpa

Can you send a kernel log for this scenario? Need to check if the sequence of closing and opening handles is clean.

Could be a memory leak elsewhere than in the driver.

Also do you see any allocation errors in kernel mode?

Naren Sankar
+1 (408) 218 6327
Broadcom Corporation

Hi

Thanks,
valpa

--
To post to this group, send email to
crystalhd-...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/crystalhd-development?hl=en


valpa

unread,
May 6, 2011, 2:58:42 AM5/6/11
to crystalhd-development
Because closing and opening handle will take about 2 seconds, I change
the code without closing/opening handle. For each movie, just close
and reopen the decode.

On May 6, 2:14 am, "Naren (Narendra) Sankar" <nsan...@broadcom.com>
wrote:

valpa

unread,
May 8, 2011, 7:51:05 PM5/8/11
to crystalhd-development
will it be a problem to keep handle opening, and close/open the
decoder consequently?

valpa

unread,
May 8, 2011, 8:01:52 PM5/8/11
to crystalhd-development
will it be a problem to keep handle opening, and close/open the
decoder consequently?



On May 6, 4:58 pm, valpa <valpass...@gmail.com> wrote:

valpa

unread,
May 9, 2011, 8:42:12 PM5/9/11
to crystalhd-development
kernel log for keep open/close the handle. I believe there is no mem
leak if handle close/open for every movie.

May 10 10:36:09 device user.info kernel: crystalhd 0000:02:00.0:
Opening new user[0] handle
May 10 10:36:11 device user.debug kernel: start_capture: pause_th:12,
resume_th:5
May 10 10:36:11 device user.info kernel: crystalhd 0000:02:00.0: [FMT
CH] PIB:0 0 420 1 780 438 780 0 0 0
May 10 10:36:11 device user.info kernel: crystalhd 0000:02:00.0:
MISSING 3 PICTURES
May 10 10:36:59 device user.info kernel: crystalhd 0000:02:00.0:
Closing user[0] handle via ioctl with mode 417a00
May 10 10:36:59 device uucp.info mediaplayer: play movie: 2.mov
May 10 10:36:59 device user.info kernel: crystalhd 0000:02:00.0:
Opening new user[0] handle
May 10 10:37:02 device user.debug kernel: start_capture: pause_th:12,
resume_th:5
May 10 10:37:02 device user.info kernel: crystalhd 0000:02:00.0: [FMT
CH] PIB:0 0 420 1 780 438 780 0 0 0
May 10 10:37:02 device user.info kernel: crystalhd 0000:02:00.0:
MISSING 3 PICTURES
May 10 10:37:08 device user.info kernel: crystalhd 0000:02:00.0:
Closing user[0] handle via ioctl with mode 417a00


When I bypass the open/close handle, the log is: (there have memory
leak)

May 10 09:55:44 device user.debug kernel: start_capture: pause_th:12,
resume_th:5
May 10 09:55:45 device user.info kernel: crystalhd 0000:02:00.0: [FMT
CH] PIB:0 0 420 1 780 438 780 0 0 0
May 10 09:55:45 device user.info kernel: crystalhd 0000:02:00.0:
MISSING 4294967198 PICTURES



Jerry


On May 6, 2:14 am, "Naren (Narendra) Sankar" <nsan...@broadcom.com>
wrote:
Reply all
Reply to author
Forward
0 new messages