| Summary: | Problems with Downloading images from Camera | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Vardhman <vardhman> |
| Component: | Import-Gphoto2 | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 0.9.0 | |
| Sentry Crash Report: | |||
|
Description
Vardhman
2006-02-10 07:06:13 UTC
This Bugzilla wizard doesn't allow me to put KDE version at 3.3 (Won't allow me to proceed if I say lesser than 3.4). So I had to put KDE 3.5 though the actual version of KDE was 3.3, but I think it hardly matters, I have had almost the latest Digikam, the libs and also the kipi-plugins from SVN almost 2 month ago at max. Are you takling about kipi camera interface plugin or digiKam camera interface ? Note kipi camera interface plugin is always disable in digiKam !!! Gilles Caulier I am taking about the one that comes from the Cameras option in digikam menubar. I recently had more problem with the same. It seems like downloading large video files is a problem, not very sure. It worked sometime and sometimes it fails.. Your camera model is a Gphoto2 or a "Mounted Camera" ? Gilles Caulier Its a USB PTP camera. So I guess it means Gphoto2 camera. ok have you a gdb backtrace of crash. You need to compile digiKam using full debug information. Also i suspect a memory leak in camera gui. Can you check this point using valgrind ? (look in HACKING file from svn the right options to use) Thanks in advance Gilles Vardhman, I have tested PTP mode with my Dynax 5D camera. Here valgrind report indeep memory problems into PTP gphoto driver during initialization : ==27810== Syscall param ioctl(generic) points to uninitialised byte(s) ==27810== at 0x1D545B69: ioctl (in /lib/tls/libc-2.3.5.so) ==27810== by 0x1DA095EF: (within /usr/lib/gphoto2_port/0.5.1/libgphoto2_port_usb.so) ==27810== Address 0x1EBFE2A4 is on thread 2's stack ==27810== ==27810== Conditional jump or move depends on uninitialised value(s) ==27810== at 0x20F6A150: camera_init (in /usr/lib/gphoto2/2.1.6/libgphoto2_ptp2.so) ==27810== ==27810== Invalid read of size 1 ==27810== at 0x20F6B22A: (within /usr/lib/gphoto2/2.1.6/libgphoto2_ptp2.so) ==27810== Address 0x1D601910 is 0 bytes after a block of size 0 alloc'd ==27810== at 0x1B900B78: calloc (vg_replace_malloc.c:279) ==27810== by 0x20F62345: ptp_usb_getdata (in /usr/lib/gphoto2/2.1.6/libgphoto2_ptp2.so) And after to have donwloaded some files and closed digiKam : 8508 (20 direct, 8488 indirect) bytes in 1 blocks are definitely lost in loss record 319 of 342 ==27810== at 0x1B8FF896: malloc (vg_replace_malloc.c:149) ==27810== by 0x1D2D62A1: gp_camera_new (in /usr/lib/libgphoto2.so.2.0.3) ==27810== ==27810== ==27810== 9067 (7704 direct, 1363 indirect) bytes in 1 blocks are definitely lost in loss record 330 of 342 ==27810== at 0x1B8FF896: malloc (vg_replace_malloc.c:149) ==27810== by 0x20F69DA7: ??? ==27810== ==27810== ==27810== 10202 bytes in 220 blocks are definitely lost in loss record 331 of 342 ==27810== at 0x1B8FF896: malloc (vg_replace_malloc.c:149) ==27810== by 0x1B8E9FC6: expand_dynamic_string_token (dl-load.c:169) ==27810== by 0x1B8EAA4A: _dl_map_object (dl-load.c:1982) ==27810== by 0x1D58183C: (within /lib/tls/libc-2.3.5.so) ==27810== by 0x1B8EF8A6: _dl_catch_error (dl-error.c:161) ==27810== by 0x1D5820F5: _dl_open (in /lib/tls/libc-2.3.5.so) ==27810== by 0x1D371D1F: (within /lib/libdl-2.3.5.so) ==27810== by 0x1B8EF8A6: _dl_catch_error (dl-error.c:161) ==27810== by 0x1D3723EE: (within /lib/libdl-2.3.5.so) ==27810== by 0x1D371D8C: dlopen (in /lib/libdl-2.3.5.so) ==27810== by 0x1D2D48FC: gp_abilities_list_load (in /usr/lib/libgphoto2.so.2.0.3) ==27810== ==27810== ==27810== 262200 bytes in 2 blocks are possibly lost in loss record 342 of 342 ==27810== at 0x1B8FF896: malloc (vg_replace_malloc.c:149) ==27810== by 0x1D50C087: opendir (in /lib/tls/libc-2.3.5.so) ==27810== by 0x1D36EA4A: GP_SYSTEM_OPENDIR (in /usr/lib/libgphoto2_port.so.0.5.1) ==27810== by 0x1BB62A61: Digikam::CameraThread::run() (cameracontroller.cpp:195) ==27810== by 0x1CAA8276: QThreadInstance::start(void*) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4) ==27810== by 0x1D54E0ED: clone (in /lib/tls/libc-2.3.5.so) ==27810== ==27810== LEAK SUMMARY: ==27810== definitely lost: 19682 bytes in 244 blocks. ==27810== indirectly lost: 20675 bytes in 305 blocks. ==27810== possibly lost: 267644 bytes in 5 blocks. ==27810== still reachable: 513744 bytes in 7991 blocks. ==27810== suppressed: 0 bytes in 0 blocks. ==27810== Reachable blocks (those to which a pointer was found) are not shown. Gilles Caulier Gilles, I was not following this bug anymore, I guess the last time I updated my kipi-plugins and other libs things seems to be fine. The video download etc is also fine. I m not sure how I can actually reproduce the bug. :( may be for time being you can set this bug fixed. On 11 Apr 2006 07:20:11 -0000, Gilles Caulier <caulier.gilles@free.fr> wrote: [bugs.kde.org quoted mail] -- Blogs: http://vardhman.blogspot.com Gilles,<br> I was not following this bug anymore, I guess the last time I updated my kipi-plugins and other libs things seems to be fine. The video download etc is also fine. I m not sure how I can actually reproduce the bug. :( may be for time being you can set this bug fixed. <br><br><div><span class="gmail_quote">On 11 Apr 2006 07:20:11 -0000, <b class="gmail_sendername">Gilles Caulier</b> <<a href="mailto:caulier.gilles@free.fr">caulier.gilles@free.fr</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> ------- You are receiving this mail because: -------<br>You are the assignee for the bug, or are watching the assignee.<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=121691">http://bugs.kde.org/show_bug.cgi?id=121691 </a><br><br><br><br><br>------- Additional Comments From caulier.gilles free fr 2006-04-11 09:20 -------<br>Vardhman,<br><br>I have tested PTP mode with my Dynax 5D camera. Here valgrind report indeep memory problems into PTP gphoto driver during initialization : <br><br>==27810== Syscall param ioctl(generic) points to uninitialised byte(s)<br>==27810== at 0x1D545B69: ioctl (in /lib/tls/libc-<a href="http://2.3.5.so">2.3.5.so</a>)<br>==27810== by 0x1DA095EF: (within /usr/lib/gphoto2_port/0.5.1/libgphoto2_port_usb.so) <br>==27810== Address 0x1EBFE2A4 is on thread 2's stack<br>==27810==<br>==27810== Conditional jump or move depends on uninitialised value(s)<br>==27810== at 0x20F6A150: camera_init (in /usr/lib/gphoto2/2.1.6/libgphoto2_ptp2.so) <br>==27810==<br>==27810== Invalid read of size 1<br>==27810== at 0x20F6B22A: (within /usr/lib/gphoto2/2.1.6/libgphoto2_ptp2.so)<br>==27810== Address 0x1D601910 is 0 bytes after a block of size 0 alloc'd<br>==27810== at 0x1B900B78: calloc (vg_replace_malloc.c:279) <br>==27810== by 0x20F62345: ptp_usb_getdata (in /usr/lib/gphoto2/2.1.6/libgphoto2_ptp2.so)<br><br>And after to have donwloaded some files and closed digiKam :<br><br>8508 (20 direct, 8488 indirect) bytes in 1 blocks are definitely lost in loss record 319 of 342 <br>==27810== at 0x1B8FF896: malloc (vg_replace_malloc.c:149)<br>==27810== by 0x1D2D62A1: gp_camera_new (in /usr/lib/libgphoto2.so.2.0.3)<br>==27810==<br>==27810==<br>==27810== 9067 (7704 direct, 1363 indirect) bytes in 1 blocks are definitely lost in loss record 330 of 342 <br>==27810== at 0x1B8FF896: malloc (vg_replace_malloc.c:149)<br>==27810== by 0x20F69DA7: ???<br>==27810==<br>==27810==<br>==27810== 10202 bytes in 220 blocks are definitely lost in loss record 331 of 342<br>==27810== at 0x1B8FF896: malloc (vg_replace_malloc.c:149) <br>==27810== by 0x1B8E9FC6: expand_dynamic_string_token (dl-load.c:169)<br>==27810== by 0x1B8EAA4A: _dl_map_object (dl-load.c:1982)<br>==27810== by 0x1D58183C: (within /lib/tls/libc-<a href="http://2.3.5.so">2.3.5.so </a>)<br>==27810== by 0x1B8EF8A6: _dl_catch_error (dl-error.c:161)<br>==27810== by 0x1D5820F5: _dl_open (in /lib/tls/libc-<a href="http://2.3.5.so">2.3.5.so</a>)<br>==27810== by 0x1D371D1F: (within /lib/libdl-<a href="http://2.3.5.so"> 2.3.5.so</a>)<br>==27810== by 0x1B8EF8A6: _dl_catch_error (dl-error.c:161)<br>==27810== by 0x1D3723EE: (within /lib/libdl-<a href="http://2.3.5.so">2.3.5.so</a>)<br>==27810== by 0x1D371D8C: dlopen (in /lib/libdl- <a href="http://2.3.5.so">2.3.5.so</a>)<br>==27810== by 0x1D2D48FC: gp_abilities_list_load (in /usr/lib/libgphoto2.so.2.0.3)<br>==27810==<br>==27810==<br>==27810== 262200 bytes in 2 blocks are possibly lost in loss record 342 of 342 <br>==27810== at 0x1B8FF896: malloc (vg_replace_malloc.c:149)<br>==27810== by 0x1D50C087: opendir (in /lib/tls/libc-<a href="http://2.3.5.so">2.3.5.so</a>)<br>==27810== by 0x1D36EA4A: GP_SYSTEM_OPENDIR (in /usr/lib/libgphoto2_port.so.0.5.1) <br>==27810== by 0x1BB62A61: Digikam::CameraThread::run() (cameracontroller.cpp:195)<br>==27810== by 0x1CAA8276: QThreadInstance::start(void*) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4)<br>==27810== by 0x1D54E0ED: clone (in /lib/tls/libc- <a href="http://2.3.5.so">2.3.5.so</a>)<br>==27810==<br>==27810== LEAK SUMMARY:<br>==27810== definitely lost: 19682 bytes in 244 blocks.<br>==27810== indirectly lost: 20675 bytes in 305 blocks.<br>==27810== possibly lost: 267644 bytes in 5 blocks. <br>==27810== still reachable: 513744 bytes in 7991 blocks.<br>==27810== suppressed: 0 bytes in 0 blocks.<br>==27810== Reachable blocks (those to which a pointer was found) are not shown.<br><br>Gilles Caulier<br> _______________________________________________<br>Digikam-devel mailing list<br><a href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/digikam-devel">https://mail.kde.org/mailman/listinfo/digikam-devel </a><br></blockquote></div><br><br clear="all"><br>-- <br>Blogs: <a href="http://vardhman.blogspot.com">http://vardhman.blogspot.com</a><br> Last time I checked valgrind is not tracking the usb ioctls correctly, so these might be irregular errors. If you get crashes, please post a gdb backtrace. Vardhman, I have fixed a little uninitialized value in camera controler witch can give unpredectible result to get Exif metadata from gphoto2 driver. Typically, Exif data are passed to camera controler like a bytes array, and the array size is uninitilaized before to test it. If there is exif data, this is not a problem because the size is updated by gphoto2, but if there is no exif data, the size is uninitialized (typically the memory content initialized by compiler). This is can be dangerous (:=)) Now the size in initialized to 0 before use it in all cases. Gilles Vardhman, Another point is the libgphoto2 version that you use. I suspect a memory leak problem on my computer about libgphoto2 (version 2.1.6-8mdk under Mandriva 2006) Have you updated libgphoto2 in your computer ? Gilles No. I only ran a SVN update on kipi-plugins AFAIR. Didn't update anything else, but the problem of downloading videos disappeared. Vardhman On 11 Apr 2006 08:04:48 -0000, Gilles Caulier <caulier.gilles@free.fr> wrote: [bugs.kde.org quoted mail] -- Blogs: http://vardhman.blogspot.com No. I only ran a SVN update on kipi-plugins AFAIR. Didn't update anything else, but the problem of downloading videos disappeared.<br><br>Vardhman<br><div><span class="gmail_quote">On 11 Apr 2006 08:04:48 -0000, <b class="gmail_sendername"> Gilles Caulier</b> <<a href="mailto:caulier.gilles@free.fr">caulier.gilles@free.fr</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> ------- You are receiving this mail because: -------<br>You are the assignee for the bug, or are watching the assignee.<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=121691">http://bugs.kde.org/show_bug.cgi?id=121691 </a><br><br><br><br><br>------- Additional Comments From caulier.gilles free fr 2006-04-11 10:04 -------<br>Vardhman,<br><br>Another point is the libgphoto2 version that you use. I suspect a memory leak problem on my computer about libgphoto2 (version 2.1.6-8mdk under Mandriva 2006)<br><br>Have you updated libgphoto2 in your computer ?<br><br>Gilles<br>_______________________________________________<br>Digikam-devel mailing list<br><a href="mailto:Digikam-devel@kde.org"> Digikam-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/digikam-devel">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br></blockquote></div><br><br clear="all"><br>-- <br>Blogs: <a href="http://vardhman.blogspot.com"> http://vardhman.blogspot.com</a><br> Vardhman, Like i have said previously, digiKam camera interface do not depand of kipi/kipi-plugins. Updated something from kipi area do not change anything in camera interface. But on my computer, i have seen some memory problems relevant of libgphoto2 and others from camera controller implementation. The last one is fixed, but just for information, i would to see witch libgphoto2 release you use on your computer ? Thanks in advance Gilles Hi Gilles, I am pasting the ouput of the command: [vardhman@linuxaddict vardhman]$ gphoto2 --version gphoto2 2.1.4 Copyright (c) 2000-2003 Lutz Mueller and others gphoto2 comes with NO WARRANTY, to the extent permitted by law. You may redistribute copies of gphoto2 under the terms of the GNU General Public License. For more information about these matters, see the files named COPYING. This version of gphoto2 is using the following software versions and options: gphoto2 2.1.4 i386-redhat-linux-gcc, popt, exif, no cdk, no aa, jpeg, readline libgphoto2 2.1.4 i386-redhat-linux-gcc, EXIF, no ltdl, /proc/meminfo libgphoto2_port 0.5.1 i386-redhat-linux-gcc, USB, serial baudboy locking, no ltdl I hope that should do. On 11 Apr 2006 09:15:01 -0000, Gilles Caulier <caulier.gilles@free.fr> wrote: [bugs.kde.org quoted mail] -- Blogs: http://vardhman.blogspot.com Hi Gilles, <br>I am pasting the ouput of the command:<br>[vardhman@linuxaddict vardhman]$ gphoto2 --version<br>gphoto2 2.1.4<br><br>Copyright (c) 2000-2003 Lutz Mueller and others<br><br>gphoto2 comes with NO WARRANTY, to the extent permitted by law. You may <br>redistribute copies of gphoto2 under the terms of the GNU General Public<br>License. For more information about these matters, see the files named COPYING.<br><br>This version of gphoto2 is using the following software versions and options: <br>gphoto2 2.1.4 i386-redhat-linux-gcc, popt, exif, no cdk, no aa, jpeg, readline<br>libgphoto2 2.1.4 i386-redhat-linux-gcc, EXIF, no ltdl, /proc/meminfo<br>libgphoto2_port 0.5.1 i386-redhat-linux-gcc, USB, serial baudboy locking, no ltdl <br><br>I hope that should do.<br><br><div><span class="gmail_quote">On 11 Apr 2006 09:15:01 -0000, <b class="gmail_sendername">Gilles Caulier</b> <<a href="mailto:caulier.gilles@free.fr">caulier.gilles@free.fr</a>> wrote: </span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br>You are the assignee for the bug, or are watching the assignee. <br><br><a href="http://bugs.kde.org/show_bug.cgi?id=121691">http://bugs.kde.org/show_bug.cgi?id=121691</a><br><br><br><br><br>------- Additional Comments From caulier.gilles free fr 2006-04-11 11:15 -------<br>Vardhman, <br><br>Like i have said previously, digiKam camera interface do not depand of kipi/kipi-plugins. Updated something from kipi area do not change anything in camera interface.<br><br>But on my computer, i have seen some memory problems relevant of libgphoto2 and others from camera controller implementation. The last one is fixed, but just for information, i would to see witch libgphoto2 release you use on your computer ? <br><br>Thanks in advance<br><br>Gilles<br>_______________________________________________<br>Digikam-devel mailing list<br><a href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/digikam-devel"> https://mail.kde.org/mailman/listinfo/digikam-devel</a><br></blockquote></div><br><br clear="all"><br>-- <br>Blogs: <a href="http://vardhman.blogspot.com">http://vardhman.blogspot.com</a><br> 2.1.4 is pretty old. Did you by chance update libusb? If you did, you need to use at least 2.1.6. yes, me i use this release : gilles@pc-caulier ~]$ gphoto2 --version gphoto2 2.1.6 Copyright (c) 2000-2004 Lutz Mueller et autres gphoto2 est livré SANS GARANTIES, tel que défini par la loi. Vous pouvez redistribuer des copies de gphoto2 sous les termes de la licence publique générale GNU. Pour plus d'informations sur ces propos, voyez les fichiers nommés COPYING. Cette version de gphoto2 utilise les versions et options des logiciels suivants: gphoto2 2.1.6 gcc, popt, exif, cdk, aa, jpeg, readline libgphoto2 2.1.6 gcc, EXIF, no ltdl, /proc/meminfo libgphoto2_port 0.5.1 gcc, USB, serial without locking, no ltdl ... and i suspect some memory problems with ptp gphoto driver, but i'm not sure... I have fixed a memory problem in camera interface. I'm sure about this point. Please, if you use a PTP camera, checkout the new implemention and test camera interface indeep, for example to download a large collection of big pictures. Thanks in advance Gilles libgphoto2 2.1.6 was caching way too much data, leading to the reported problems... We have fixed this for the upcoming 2.2 release. Marcus, This is want mean that we need to wait 2.2 release before to close this file ? Currently, i download 1 Gb of RAW files from my Dynax 5D in PTP mode using gdb. I will check if any crash can be reproduce and if memory usage is normal. And i will re-iterate the download at any time to validate. Vardhman, can you do a similar test in your computer ? Thanks in advance Gilles Vardhman, I have tested to download over 1Gb of pictures from my Dynax 5D in PTP mode using libgphoto 2.2 (Suse 10.1). All work fine here (reproduce 3x1Gb to download) I close this file now. Gilles |