[Bug 147750] New: Crash SIGSEGV every time I want to scan my HD

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147750         
           Summary: Crash SIGSEGV every time I want to scan my HD
           Product: digikam
           Version: 0.9.1
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: sun.wukong rx3 net


Version:           0.9.1 (using KDE KDE 3.5.7)
Installed from:    Ubuntu Packages
Compiler:          Ubuntu/Canonical's used for KDE 3.5.7 and Digikam 0.9.1 Kubuntu Feisty Fawn (upgraded from Edgy Eft)
OS:                Linux

Procedure that can be reproduced any time :

Start digikam 0.9.1
A new album is defined in /home/myself/Album
Menu Camera/Media Browse/
Select external USB hard drive where I store my pictures
Scanning occurs, displaying :
   "Listing files in /media/HD_Photos/.....   is complete
The PC is working hard : the mouse mouvement is no more smooth, the display isn't refreshed nicely. Big job (even for Core2Duo E6600 and 2Go RAM).
"top" says nearly 20%CPU and 78%Mem.
The process indicator doesn't change and stays on "0%".

Suddenly, the PC starts to respond much better and the crash window appears :-(

The external USB HD is 60Go and ext3 FS.

To prevent scanning the whole volume, I chown'ed and chmod'ed all top-directories but the one with the pictures. That way, only 11Go are concerned, about 13500 files.

The crash windows isn't very talkative:
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".


Launched from Konsole, I get this extra info:
In file kernel/qimage.cpp, line 1297: Out of memory
In file kernel/qimage.cpp, line 1297: Out of memory
In file kernel/qimage.cpp, line 1297: Out of memory
[...]
In file kernel/qimage.cpp, line 1297: Out of memory
In file kernel/qpixmap_x11.cpp, line 747: Out of memory
In file kernel/qimage.cpp, line 1297: Out of memory
KCrash: Application 'digikam' crashing...
Alarm clock
myself comp

I am available for extra test if you wish (but won't be from July 18th to 22th included)
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147750         




------- Additional Comments From caulier.gilles gmail com  2007-07-10 18:00 -------
Sun,

Sound like a device problem in your computer (memory ? HDD corrupted ?)

We have never seen something like that in this room...

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147750         




------- Additional Comments From sun.wukong rx3 net  2007-07-11 01:03 -------
I tried the same HD on another platform : Sempron2400/512Mo
It took ages. The scanning (was it ?) was veeeerrrrrry long (several hours). The PC was unusable as it seems all the CPU was dedicated to the process. To save power, I shutted down the CRT.
When I noticed the main HD LED wasn't flashing anymore, I had a look but there were nothing to see : no more digiKam windows (nor process), no crash window. Just a Konsole session and a Konqueror instance that were already there.

I'll make some test next week, as follow :
* copy the picture on another HD (USB or IDE)
* run digikam on that copy. "Unfortunatly" it seems there's no way to scan only a folder and that the whole device is to be scanned. Is that right ?
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147750         




------- Additional Comments From caulier.gilles gmail com  2007-08-24 22:15 -------
Sun,

Some fresh new about this report. It still valid ?

Arnd, if user do not give response, i propose to close it...

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Arnd Baecker]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147750         
arnd.baecker web de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From arnd.baecker web de  2007-11-05 10:26 -------
Without additional input nothing can be done. Closing this bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel