[Bug 278049] New: Crash during tagging while scanning run in background
Locked
12345
12345
[digikam] [Bug 278049] Crash during tagging while scanning run in background
 
|
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #55 from Kai Krakow <[hidden email]> --- Created attachment 78912 --> https://bugs.kde.org/attachment.cgi?id=78912&action=edit New crash information added by DrKonqi digikam (3.0.0) on KDE Platform 4.10.1 using Qt 4.8.4 - What I was doing when the application crashed: I started face recognition and most times this results in a crash - not immediatly but after some time. I don't see any feedback on the scanning process running, just the hard disk starts working. -- Backtrace (Reduced): #6 0x00007ff66675fb65 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007ff666760fdb in __GI_abort () at abort.c:91 [...] #9 0x00007ff6667a5456 in malloc_printerr (action=3, str=0x7ff666892c98 "double free or corruption (!prev)", ptr=<optimized out>) at malloc.c:5007 #10 0x00007ff66a1b4df0 in node_destruct (n=0x70bfb90, this=<optimized out>) at /usr/include/qt4/QtCore/qlist.h:388 #11 erase (alast=..., afirst=..., this=0x33e5858) at /usr/include/qt4/QtCore/qlist.h:811 -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #56 from Gilles Caulier <[hidden email]> --- *** Bug 321273 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
I have tagged some pictures with face detection. In Background face scanning
was active.
learn-spanish-now [url=http://learn-spanish-now.com/]http://www.learn-spanish-now.com/[/url]
nowleather [url=http://www.nowleather.co.uk/]nowleather best leather jackets[/url] |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #57 from Lucas Linard <[hidden email]> --- Created attachment 80859 --> https://bugs.kde.org/attachment.cgi?id=80859&action=edit New crash information added by DrKonqi digikam (3.2.0) on KDE Platform 4.10.3 "release 1" using Qt 4.8.4 - What I was doing when the application crashed: running face detect tool with detailed progress -- Backtrace (Reduced): #6 0x00007f581c1b5b88 in clear (d=0x8eaa710) at kernel/qvariant.cpp:290 #7 0x00007f581decd931 in node_destruct (n=0x74c9f48, this=<optimized out>) at /usr/include/QtCore/qlist.h:388 #8 erase (alast=..., afirst=..., this=0x275f4e8) at /usr/include/QtCore/qlist.h:811 #9 Digikam::ImageModel::removeRowPairs (this=this@entry=0x275d040, toRemove=...) at /usr/src/debug/digikam-3.2.0/core/libs/models/imagemodel.cpp:1025 #10 0x00007f581decf85d in Digikam::ImageModel::finishIncrementalRefresh (this=0x275d040) at /usr/src/debug/digikam-3.2.0/core/libs/models/imagemodel.cpp:844 -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #58 from Gilles Caulier <[hidden email]> --- *** Bug 321851 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #59 from Gilles Caulier <[hidden email]> --- *** Bug 323428 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #60 from Gilles Caulier <[hidden email]> --- *** Bug 323823 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #61 from Gilles Caulier <[hidden email]> --- *** Bug 323828 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
Jonathan Mast <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #62 from Jonathan Mast <[hidden email]> --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #63 from Flu87 <[hidden email]> --- Also crashes, when I didn't scan, but changed recognized faces and canceled the rebuilding of the face database (Setting Faces Map?) btw. that uses 14GB RAM oO -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
Alexander Meshcheryakov <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #64 from Alexander Meshcheryakov <[hidden email]> --- Flu87, it seems you have been hit by https://bugs.kde.org/show_bug.cgi?id=323888 -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #65 from Lucas Linard <[hidden email]> --- Created attachment 82599 --> https://bugs.kde.org/attachment.cgi?id=82599&action=edit New crash information added by DrKonqi digikam (3.4.0) on KDE Platform 4.11.1 using Qt 4.8.5 - What I was doing when the application crashed: Trying to use face detect tool to try to rescan the files with no confirmation - Unusual behavior I noticed: Simply Crashes. -- Backtrace (Reduced): #6 0x0000003421b9d70b in clear (d=0x5d16c30) at kernel/qvariant.cpp:290 #7 0x000000344ff35c11 in node_destruct (this=<optimized out>, n=0x5948158) at /usr/include/QtCore/qlist.h:388 #8 erase (alast=..., afirst=..., this=0x2062b18) at /usr/include/QtCore/qlist.h:803 #9 Digikam::ImageModel::removeRowPairs (this=this@entry=0x20606a0, toRemove=...) at /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:1025 #10 0x000000344ff36ec2 in Digikam::ImageModel::finishIncrementalRefresh (this=this@entry=0x20606a0) at /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:844 -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
Hello,
Should you do face confirmation without launching anything else out or in digikam (no scanning ...) and see if it crash ? -restart the computer, launch digikam in gdb and do face tag confirmation Should you give the result of $cat /proc/cpuinfo ? cordialement, Eric Le mercredi 02 octobre 2013 à 00:34 +0000, Lucas Linard a écrit : > https://bugs.kde.org/show_bug.cgi?id=278049 > > --- Comment #65 from Lucas Linard <[hidden email]> --- > Created attachment 82599 > --> https://bugs.kde.org/attachment.cgi?id=82599&action=edit > New crash information added by DrKonqi > > digikam (3.4.0) on KDE Platform 4.11.1 using Qt 4.8.5 > > - What I was doing when the application crashed: > Trying to use face detect tool to try to rescan the files with no confirmation > > - Unusual behavior I noticed: > Simply Crashes. > > -- Backtrace (Reduced): > #6 0x0000003421b9d70b in clear (d=0x5d16c30) at kernel/qvariant.cpp:290 > #7 0x000000344ff35c11 in node_destruct (this=<optimized out>, n=0x5948158) at > /usr/include/QtCore/qlist.h:388 > #8 erase (alast=..., afirst=..., this=0x2062b18) at > /usr/include/QtCore/qlist.h:803 > #9 Digikam::ImageModel::removeRowPairs (this=this@entry=0x20606a0, > toRemove=...) at > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:1025 > #10 0x000000344ff36ec2 in Digikam::ImageModel::finishIncrementalRefresh > (this=this@entry=0x20606a0) at > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:844 > _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #66 from [hidden email] --- Hello, Should you do face confirmation without launching anything else out or in digikam (no scanning ...) and see if it crash ? -restart the computer, launch digikam in gdb and do face tag confirmation Should you give the result of $cat /proc/cpuinfo ? cordialement, Eric Le mercredi 02 octobre 2013 à 00:34 +0000, Lucas Linard a écrit : > https://bugs.kde.org/show_bug.cgi?id=278049 > > --- Comment #65 from Lucas Linard <[hidden email]> --- > Created attachment 82599 > --> https://bugs.kde.org/attachment.cgi?id=82599&action=edit > New crash information added by DrKonqi > > digikam (3.4.0) on KDE Platform 4.11.1 using Qt 4.8.5 > > - What I was doing when the application crashed: > Trying to use face detect tool to try to rescan the files with no confirmation > > - Unusual behavior I noticed: > Simply Crashes. > > -- Backtrace (Reduced): > #6 0x0000003421b9d70b in clear (d=0x5d16c30) at kernel/qvariant.cpp:290 > #7 0x000000344ff35c11 in node_destruct (this=<optimized out>, n=0x5948158) at > /usr/include/QtCore/qlist.h:388 > #8 erase (alast=..., afirst=..., this=0x2062b18) at > /usr/include/QtCore/qlist.h:803 > #9 Digikam::ImageModel::removeRowPairs (this=this@entry=0x20606a0, > toRemove=...) at > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:1025 > #10 0x000000344ff36ec2 in Digikam::ImageModel::finishIncrementalRefresh > (this=this@entry=0x20606a0) at > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:844 > -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #67 from Lucas Linard <[hidden email]> --- How do I launch digikam from gdb. I'm no developer just a regular user trying to help. What can I do? [llinard@Inspiron ~]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz stepping : 9 microcode : 0x19 cpu MHz : 1674.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 3591.83 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz stepping : 9 microcode : 0x19 cpu MHz : 1692.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 3591.83 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz stepping : 9 microcode : 0x19 cpu MHz : 1782.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 3591.83 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz stepping : 9 microcode : 0x19 cpu MHz : 1710.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 3591.83 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: > From: [hidden email] > To: [hidden email] > Subject: [digikam] [Bug 278049] Crash during tagging while scanning run in background > Date: Wed, 2 Oct 2013 07:36:57 +0000 > > https://bugs.kde.org/show_bug.cgi?id=278049 > > --- Comment #66 from [hidden email] --- > Hello, > > Should you do face confirmation without launching anything else out or > in digikam (no scanning ...) and see if it crash ? > > -restart the computer, launch digikam in gdb and do face tag > confirmation > > Should you give the result of $cat /proc/cpuinfo ? > > cordialement, > > Eric > > > > Le mercredi 02 octobre 2013 à 00:34 +0000, Lucas Linard a écrit : > > https://bugs.kde.org/show_bug.cgi?id=278049 > > > > --- Comment #65 from Lucas Linard <[hidden email]> --- > > Created attachment 82599 > > --> https://bugs.kde.org/attachment.cgi?id=82599&action=edit > > New crash information added by DrKonqi > > > > digikam (3.4.0) on KDE Platform 4.11.1 using Qt 4.8.5 > > > > - What I was doing when the application crashed: > > Trying to use face detect tool to try to rescan the files with no confirmation > > > > - Unusual behavior I noticed: > > Simply Crashes. > > > > -- Backtrace (Reduced): > > #6 0x0000003421b9d70b in clear (d=0x5d16c30) at kernel/qvariant.cpp:290 > > #7 0x000000344ff35c11 in node_destruct (this=<optimized out>, n=0x5948158) at > > /usr/include/QtCore/qlist.h:388 > > #8 erase (alast=..., afirst=..., this=0x2062b18) at > > /usr/include/QtCore/qlist.h:803 > > #9 Digikam::ImageModel::removeRowPairs (this=this@entry=0x20606a0, > > toRemove=...) at > > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:1025 > > #10 0x000000344ff36ec2 in Digikam::ImageModel::finishIncrementalRefresh > > (this=this@entry=0x20606a0) at > > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:844 > > > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
Hello,
Should you give a copy of digikam components : in digikam : menu help then component, copy and paste the list ? Where are your collection, on local disk or on a network share ? For gdb you should install it if it is not. But wait for the moment. Greatings, Eric Le mercredi 02 octobre 2013 à 13:15 +0000, Lucas Linard a écrit : > https://bugs.kde.org/show_bug.cgi?id=278049 > > --- Comment #67 from Lucas Linard <[hidden email]> --- > How do I launch digikam from gdb. I'm no developer just a regular user trying > to help. What can I do? > > [llinard@Inspiron ~]$ cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 58 > model name : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz > stepping : 9 > microcode : 0x19 > cpu MHz : 1674.000 > cache size : 3072 KB > physical id : 0 > siblings : 4 > core id : 0 > cpu cores : 2 > apicid : 0 > initial apicid : 0 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm > constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc > aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 > xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c > lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept > vpid fsgsbase smep erms > bogomips : 3591.83 > clflush size : 64 > cache_alignment : 64 > address sizes : 36 bits physical, 48 bits virtual > power management: > > processor : 1 > vendor_id : GenuineIntel > cpu family : 6 > model : 58 > model name : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz > stepping : 9 > microcode : 0x19 > cpu MHz : 1692.000 > cache size : 3072 KB > physical id : 0 > siblings : 4 > core id : 1 > cpu cores : 2 > apicid : 2 > initial apicid : 2 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm > constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc > aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 > xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c > lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept > vpid fsgsbase smep erms > bogomips : 3591.83 > clflush size : 64 > cache_alignment : 64 > address sizes : 36 bits physical, 48 bits virtual > power management: > > processor : 2 > vendor_id : GenuineIntel > cpu family : 6 > model : 58 > model name : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz > stepping : 9 > microcode : 0x19 > cpu MHz : 1782.000 > cache size : 3072 KB > physical id : 0 > siblings : 4 > core id : 0 > cpu cores : 2 > apicid : 1 > initial apicid : 1 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm > constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc > aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 > xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c > lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept > vpid fsgsbase smep erms > bogomips : 3591.83 > clflush size : 64 > cache_alignment : 64 > address sizes : 36 bits physical, 48 bits virtual > power management: > > processor : 3 > vendor_id : GenuineIntel > cpu family : 6 > model : 58 > model name : Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz > stepping : 9 > microcode : 0x19 > cpu MHz : 1710.000 > cache size : 3072 KB > physical id : 0 > siblings : 4 > core id : 1 > cpu cores : 2 > apicid : 3 > initial apicid : 3 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm > constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc > aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 > xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c > lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept > vpid fsgsbase smep erms > bogomips : 3591.83 > clflush size : 64 > cache_alignment : 64 > address sizes : 36 bits physical, 48 bits virtual > power management: > > > > From: [hidden email] > > To: [hidden email] > > Subject: [digikam] [Bug 278049] Crash during tagging while scanning run in background > > Date: Wed, 2 Oct 2013 07:36:57 +0000 > > > > https://bugs.kde.org/show_bug.cgi?id=278049 > > > > --- Comment #66 from [hidden email] --- > > Hello, > > > > Should you do face confirmation without launching anything else out or > > in digikam (no scanning ...) and see if it crash ? > > > > -restart the computer, launch digikam in gdb and do face tag > > confirmation > > > > Should you give the result of $cat /proc/cpuinfo ? > > > > cordialement, > > > > Eric > > > > > > > > Le mercredi 02 octobre 2013 à 00:34 +0000, Lucas Linard a écrit : > > > https://bugs.kde.org/show_bug.cgi?id=278049 > > > > > > --- Comment #65 from Lucas Linard <[hidden email]> --- > > > Created attachment 82599 > > > --> https://bugs.kde.org/attachment.cgi?id=82599&action=edit > > > New crash information added by DrKonqi > > > > > > digikam (3.4.0) on KDE Platform 4.11.1 using Qt 4.8.5 > > > > > > - What I was doing when the application crashed: > > > Trying to use face detect tool to try to rescan the files with no confirmation > > > > > > - Unusual behavior I noticed: > > > Simply Crashes. > > > > > > -- Backtrace (Reduced): > > > #6 0x0000003421b9d70b in clear (d=0x5d16c30) at kernel/qvariant.cpp:290 > > > #7 0x000000344ff35c11 in node_destruct (this=<optimized out>, n=0x5948158) at > > > /usr/include/QtCore/qlist.h:388 > > > #8 erase (alast=..., afirst=..., this=0x2062b18) at > > > /usr/include/QtCore/qlist.h:803 > > > #9 Digikam::ImageModel::removeRowPairs (this=this@entry=0x20606a0, > > > toRemove=...) at > > > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:1025 > > > #10 0x000000344ff36ec2 in Digikam::ImageModel::finishIncrementalRefresh > > > (this=this@entry=0x20606a0) at > > > /usr/src/debug/digikam-3.4.0/core/libs/models/imagemodel.cpp:844 > > > > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. > _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #68 from Gilles Caulier <[hidden email]> --- Look here : http://www.digikam.org/contrib Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #69 from Gilles Caulier <[hidden email]> --- digiKam 3.5.0 is out. Can you give a fresh feedback about your report ? Crash still reproducible ? Thanks in advance Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
--- Comment #70 from Pete Beardmore <[hidden email]> --- Created attachment 83863 --> https://bugs.kde.org/attachment.cgi?id=83863&action=edit gdb full backtrace KDEBUG=1 gdb bt full for git version 2013Dec01 @ 3c1c6475bec2edd1bac4125c2c4a42d45dd7213d -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
[digikam] [Bug 278049] Crash during tagging while scanning run in background
|
|
In reply to this post by Bugzilla from The_Akki@gmx.de
https://bugs.kde.org/show_bug.cgi?id=278049
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|3.1.0 |4.0.0-beta1 -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
«
Return to digikam-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |