Bug 282124 - Nepomuk crash while browsing with Iceweasel
Summary: Nepomuk crash while browsing with Iceweasel
Status: RESOLVED DUPLICATE of bug 275880
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
: 269135 270643 275169 275553 276125 276242 276373 276903 277419 277513 278520 278789 279927 280203 281587 281868 282724 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-09-16 08:15 UTC by David Eccles (gringer)
Modified: 2011-10-11 19:14 UTC (History)
19 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (11.32 KB, text/plain)
2011-09-16 08:30 UTC, David Eccles (gringer)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Eccles (gringer) 2011-09-16 08:15:20 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.3
Operating System: Linux 3.0.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:
Browsing wikipedia, google searches, and running a few shell scripts. One (of 12) CPU was running near 100%, but no other heavy services were running.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Nepomuk Service Stub (nepomukservicestub), signal: Aborted
__lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
	in ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S
[Current thread is 1 (Thread 0x7f17053e2760 (LWP 25518))]

Thread 3 (Thread 0x7f16f39f5700 (LWP 25520)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f1704deb0bb in wait (time=18446744073709551615, this=0x1aa76b0) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x1aa7ee0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00007f16f4054a61 in Nepomuk::IndexFeeder::run (this=0x1aa7ec0) at ../../../../nepomuk/services/strigi/nepomukindexfeeder.cpp:188
#4  0x00007f1704deac25 in QThreadPrivate::start (arg=0x1aa7ec0) at thread/qthread_unix.cpp:320
#5  0x00007f1702730b40 in start_thread (arg=<optimized out>) at pthread_create.c:304
#6  0x00007f1702a1b36d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f16ee678700 (LWP 25521)):
[KCrash Handler]
#6  0x00007f1702978405 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f170297b680 in *__GI_abort () at abort.c:92
#8  0x00007f17029aedbb in __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9  0x00007f17029b8606 in malloc_printerr (action=3, str=0x7f1702a8c2f7 "invalid fastbin entry (free)", ptr=<optimized out>) at malloc.c:6283
#10 0x00007f17029bd33c in *__GI___libc_free (mem=<optimized out>) at malloc.c:3738
#11 0x00007f1704e2eabc in QString::free (d=0x1c76450) at tools/qstring.cpp:1185
#12 0x00007f1704eac926 in ~QString (this=0x7f16ee677910, __in_chrg=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qstring.h:883
#13 QFSFileEngine::fileFlags (this=0x1cce400, type=...) at io/qfsfileengine_unix.cpp:879
#14 0x00007f1704e6ab76 in QFileInfoPrivate::getFileFlags (this=0x1b791a0, request=...) at io/qfileinfo.cpp:126
#15 0x00007f1704e6c3ae in QFileInfo::isHidden (this=<optimized out>) at io/qfileinfo.cpp:861
#16 0x00007f1704e652b3 in QDirIteratorPrivate::matchesFilters (this=0x7f16e00022f0, fileName=..., fi=...) at io/qdiriterator.cpp:318
#17 0x00007f1704e65afe in QDirIteratorPrivate::advance (this=0x7f16e00022f0) at io/qdiriterator.cpp:222
#18 0x00007f1704e65c7d in QDirIterator::next (this=0x7f16ee677ba0) at io/qdiriterator.cpp:457
#19 0x00007f16f404927a in Nepomuk::IndexScheduler::analyzeDir (this=0x1a39e30, dir_=<optimized out>, flags=...) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:391
#20 0x00007f16f404b72c in Nepomuk::IndexScheduler::run (this=0x1a39e30) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:338
#21 0x00007f1704deac25 in QThreadPrivate::start (arg=0x1a39e30) at thread/qthread_unix.cpp:320
#22 0x00007f1702730b40 in start_thread (arg=<optimized out>) at pthread_create.c:304
#23 0x00007f1702a1b36d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#24 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f17053e2760 (LWP 25518)):
#0  __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
#1  0x00007f17029bf192 in _L_lock_11440 () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f17029be4d4 in *__GI___libc_realloc (oldmem=0x7f1702cc5e60, bytes=120) at malloc.c:3813
#3  0x00007f1704e16dba in QRegExpMatchState::prepareForMatch (this=0x1bd3330, eng=0x1bd4060) at tools/qregexp.cpp:1379
#4  0x00007f1704e23c91 in prepareEngineForMatch (priv=0x1bd3300, str=...) at tools/qregexp.cpp:3727
#5  0x00007f1704e23ed4 in QRegExp::exactMatch (this=0x1bf3198, str=...) at tools/qregexp.cpp:4068
#6  0x00007f16f3e097af in RegExpCache::exactMatch (this=<optimized out>, s=...) at ../../../nepomuk/common/regexpcache.cpp:40
#7  0x00007f16f404ca3d in Nepomuk::StrigiServiceConfig::shouldFileBeIndexed (this=<optimized out>, fileName=<optimized out>) at ../../../../nepomuk/services/strigi/strigiserviceconfig.cpp:177
#8  0x00007f16f404cbb4 in shouldFolderBeIndexed (path=..., this=0x1b70570) at ../../../../nepomuk/services/strigi/strigiserviceconfig.cpp:166
#9  Nepomuk::StrigiServiceConfig::shouldFolderBeIndexed (this=0x1b70570, path=...) at ../../../../nepomuk/services/strigi/strigiserviceconfig.cpp:148
#10 0x00007f16f4045880 in Nepomuk::StrigiService::updateFolder (this=0x1a342c0, path=..., recursive=false, forced=false) at ../../../../nepomuk/services/strigi/strigiservice.cpp:231
#11 0x00007f16f4057e2d in StrigiAdaptor::qt_metacall (this=0x1b92480, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0x7fffdc70b6a0) at strigiadaptor.moc:157
#12 0x00007f1704b089b1 in QDBusConnectionPrivate::deliverCall (this=0x19a1dc0, object=0x1b92480, msg=..., metaTypes=..., slotIdx=19) at qdbusintegrator.cpp:941
#13 0x00007f1704b09afd in QDBusConnectionPrivate::activateCall (this=0x19a1dc0, object=0x1b92480, flags=337, msg=...) at qdbusintegrator.cpp:851
#14 0x00007f1704b0a3d2 in QDBusConnectionPrivate::activateObject (this=0x19a1dc0, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1409
#15 0x00007f1704b0a4a8 in QDBusActivateObjectEvent::placeMetaCall (this=0x7f16e000cff0) at qdbusintegrator.cpp:1523
#16 0x00007f1704ee787a in QObject::event (this=0x1a342c0, e=<optimized out>) at kernel/qobject.cpp:1217
#17 0x00007f17031de9f4 in notify_helper (e=0x7f16e000cff0, receiver=0x1a342c0, this=0x19109f0) at kernel/qapplication.cpp:4467
#18 QApplicationPrivate::notify_helper (this=0x19109f0, receiver=0x1a342c0, e=0x7f16e000cff0) at kernel/qapplication.cpp:4439
#19 0x00007f17031e3881 in QApplication::notify (this=0x7fffdc70c580, receiver=0x1a342c0, e=0x7f16e000cff0) at kernel/qapplication.cpp:4346
#20 0x00007f17041e0a66 in KApplication::notify (this=0x7fffdc70c580, receiver=0x1a342c0, event=0x7f16e000cff0) at ../../kdeui/kernel/kapplication.cpp:311
#21 0x00007f1704ed116c in QCoreApplication::notifyInternal (this=0x7fffdc70c580, receiver=0x1a342c0, event=0x7f16e000cff0) at kernel/qcoreapplication.cpp:731
#22 0x00007f1704ed4528 in sendEvent (event=0x7f16e000cff0, receiver=0x1a342c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#23 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x18f35d0) at kernel/qcoreapplication.cpp:1372
#24 0x00007f1704efb843 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#25 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:277
#26 0x00007f1701c574a3 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#27 0x00007f1701c57c80 in ?? () from /lib/libglib-2.0.so.0
#28 0x00007f1701c57f1d in g_main_context_iteration () from /lib/libglib-2.0.so.0
#29 0x00007f1704efbc9f in QEventDispatcherGlib::processEvents (this=0x18f4c90, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#30 0x00007f1703282a4e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x00007f1704ed0372 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#32 0x00007f1704ed056f in QEventLoop::exec (this=0x7fffdc70c3f0, flags=...) at kernel/qeventloop.cpp:201
#33 0x00007f1704ed4717 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#34 0x0000000000403c1f in main (argc=2, argv=0x7fffdc70ca18) at ../../../nepomuk/servicestub/main.cpp:167

This bug may be a duplicate of or related to bug 281664, bug 281223, bug 280633.

Possible duplicates by query: bug 282076, bug 281664, bug 281587, bug 281356, bug 281355.

Reported using DrKonqi
Comment 1 David Eccles (gringer) 2011-09-16 08:30:03 UTC
Created attachment 63681 [details]
New crash information added by DrKonqi

nepomukservicestub (0.2) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.3

- What I was doing when the application crashed:
Same programs running as previously, browsing yeast database using Iceweasel

-- Backtrace (Reduced):
#8  0x00007fa67f356dbb in __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9  0x00007fa67f360606 in malloc_printerr (action=3, str=0x7fa67f4374e8 "malloc(): memory corruption (fast)", ptr=<optimized out>) at malloc.c:6283
#10 0x00007fa67f363ee8 in _int_malloc (av=0x7fa67f66de60, bytes=<optimized out>) at malloc.c:4308
[...]
#12 0x00007fa6817d3be5 in QString::QString (this=0x7fa666fca9d0, size=10) at tools/qstring.cpp:1099
#13 0x00007fa6818ac978 in QUtf8::convertToUnicode (chars=<optimized out>, len=9, state=0x0) at codecs/qutfcodec.cpp:183
Comment 2 Sebastian Trueg 2011-09-19 10:02:56 UTC
Can this be reproduced with KDE 4.7?
Comment 3 Sebastian Trueg 2011-09-19 19:26:58 UTC
*** Bug 281868 has been marked as a duplicate of this bug. ***
Comment 4 Sebastian Trueg 2011-09-19 19:29:25 UTC
*** Bug 280203 has been marked as a duplicate of this bug. ***
Comment 5 Sebastian Trueg 2011-09-19 19:29:51 UTC
*** Bug 279927 has been marked as a duplicate of this bug. ***
Comment 6 Sebastian Trueg 2011-09-19 19:31:04 UTC
*** Bug 278789 has been marked as a duplicate of this bug. ***
Comment 7 Sebastian Trueg 2011-09-19 19:34:16 UTC
*** Bug 277419 has been marked as a duplicate of this bug. ***
Comment 8 Sebastian Trueg 2011-09-19 19:35:04 UTC
*** Bug 276903 has been marked as a duplicate of this bug. ***
Comment 9 David Eccles (gringer) 2011-09-20 07:52:33 UTC
> Can this be reproduced with KDE 4.7?

I don't know. I don't have the luxury of trying this until Debian allows newer versions into their repositories. 

I'm no longer getting crashes since upgrading a couple of days ago. Here are the Debian versions of packages on my computer now that I expect might be relevant:

$ aptitude show libnepomuk4 libqtcore4 kde-full | grep '\(Package\|Version\)'
Package: libnepomuk4
Version: 4:4.6.5-2
Package: libqtcore4
Version: 4:4.7.3-8
Package: kde-full
Version: 5:70
Comment 10 Sebastian Trueg 2011-09-20 08:21:15 UTC
*** Bug 276242 has been marked as a duplicate of this bug. ***
Comment 11 Sebastian Trueg 2011-09-20 12:24:22 UTC
*** Bug 278520 has been marked as a duplicate of this bug. ***
Comment 12 Sebastian Trueg 2011-09-20 12:25:21 UTC
*** Bug 276125 has been marked as a duplicate of this bug. ***
Comment 13 Sebastian Trueg 2011-09-20 12:25:35 UTC
*** Bug 275553 has been marked as a duplicate of this bug. ***
Comment 14 Sebastian Trueg 2011-09-20 12:29:40 UTC
*** Bug 275169 has been marked as a duplicate of this bug. ***
Comment 15 Sebastian Trueg 2011-09-20 12:30:05 UTC
*** Bug 270643 has been marked as a duplicate of this bug. ***
Comment 16 Sebastian Trueg 2011-09-20 12:30:17 UTC
*** Bug 269135 has been marked as a duplicate of this bug. ***
Comment 17 Sebastian Trueg 2011-09-20 12:31:24 UTC
*** Bug 281587 has been marked as a duplicate of this bug. ***
Comment 18 Sebastian Trueg 2011-09-20 12:32:51 UTC
*** Bug 276373 has been marked as a duplicate of this bug. ***
Comment 19 Tigz Mordan 2011-09-21 12:22:08 UTC
I no longer use Linux, and so no longer need to be informed of progress on this problem.
Comment 20 David Eccles (gringer) 2011-09-23 08:49:51 UTC
More crashes, this time using a vesa Xorg driver -- I previously thought the bugs might have something to do with using the non-free nvidia drivers (this was because loading eclipse and localc caused a Xorg reset), so I'm in the process of getting nouveau drivers for my video card. Same versions of packages as above in comment 9.
Comment 21 Sebastian Trueg 2011-09-23 09:23:12 UTC
(In reply to comment #20)
> More crashes, this time using a vesa Xorg driver -- I previously thought the
> bugs might have something to do with using the non-free nvidia drivers (this
> was because loading eclipse and localc caused a Xorg reset), so I'm in the
> process of getting nouveau drivers for my video card. Same versions of packages
> as above in comment 9.

this is still not KDE 4.7 I assume?
Comment 22 David Eccles (gringer) 2011-09-23 10:01:38 UTC
On 23/09/11 11:23, Sebastian Trueg wrote:
>> Same versions of packages as above in comment 9.
> this is still not KDE 4.7 I assume?

Yes, I believe so. The version numbering for KDE in Debian is a little 
odd, but the versions for most KDE things seem to match the platform 
version in the initial bug report.
Comment 23 Sebastian Trueg 2011-09-26 07:05:43 UTC
*** Bug 282724 has been marked as a duplicate of this bug. ***
Comment 24 Sven Eden 2011-09-27 10:47:43 UTC
I just wanted to add, that I get a segmentation fault of nepomukservicestub since I added folders which reside in TrueCrypt containers to the search list of strigi. No idea whether this is relevant, but this might be:

1.: I am using KDE-4.7.1 with QT-4.7.4
2.: Everything on my system is built with -ggdb, but drkonqi can't get a backtrace. Nothing.

I have already cleaned the nepomuk database files in ~/.kde4/share/apps/nepomuk/repository/main/data/virtuosobackend/, but a few seconds after KDE starts up, the segfault is back.

Hopefully I succeed in finding out why drkonqi all of a sudden is free of any backtrace, and then I'll report back.
Comment 25 Sven Eden 2011-09-27 14:32:02 UTC
Five minutes ago I wanted to report that the problem is fixed by deleting the virtuoso data files again, upgrading strigi to version 0.7.6 and rebooting the machine.

It started up fine, no crash in sight, nepomuk/strigi/akonadi working like a charm (unless you count in the fact that akonadi_nepomu_email_feeder ate up nearly 6 GB of memory, see Bug 279800).

But now, after another restart, I get the segmentation fault again after starting Akonadi Server. All that drKonqi could produce was this:

------------
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.7.1 (4.7.1) (Compiled from sources)
Qt Version: 4.7.4
Operating System: Linux 3.0.4-gentoo x86_64

-- Information about the crash:
<Erklären Sie bitte ganz genau, was Sie machten, als das Programm abstürzte.>

The crash can be reproduced some of the time.

-- Backtrace:
A useful backtrace could not be generated

An https://bugs.kde.org berichten
------------

The "Backtrace" is nothing but this line:

------------
Application: Nepomuk-Dienst (nepomukservicestub), signal: Segmentation fault
------------

I am completely at sea how to generate a useful Backtrace. :-(


======

One thing is odd: There _are_ instances of nepomukservicestub currently running. But which should be there now and isn't?

------------
sed@sed-notebook ~ $ ps xfa | grep nepomuk | grep -v grep
 4573 ?        Sl     0:00 /usr/bin/nepomukserver
 4590 ?        SNl    0:03  \_ /usr/bin/nepomukservicestub nepomukstorage
 4838 ?        SN     0:00  \_ /usr/bin/nepomukservicestub nepomukbackupsync
 4846 ?        SNl    0:00  \_ /usr/bin/nepomukservicestub nepomukfilewatch
 4847 ?        SN     0:00  \_ /usr/bin/nepomukservicestub nepomukqueryservice
 5144 ?        SNl    0:01  \_ /usr/bin/nepomukservicestub nepomukstrigiservice
 4668 ?        S      0:00 /usr/bin/nepomukcontroller -session 10143143147fd000131711977700000042090027_1317131989_395876
 5095 ?        S      0:00  \_ /usr/bin/akonadi_nepomuk_calendar_feeder --identifier akonadi_nepomuk_calendar_feeder
 5096 ?        S      0:00  \_ /usr/bin/akonadi_nepomuk_contact_feeder --identifier akonadi_nepomuk_contact_feeder
 5097 ?        S      0:00  \_ /usr/bin/akonadi_nepomuk_email_feeder --identifier akonadi_nepomuk_email_feeder
------------
Comment 26 Sven Eden 2011-09-27 14:45:07 UTC
OH NO! I have posted in the wrong browser tab showing duplicate Bug 282724 ! Please forgive me posting again (and something that might be completely unrelated) but I have no idea whether comments can be "moved" or not. :-(

I have seen something rather disturbing. In akonadiconsole I can see that my
LDAP Adress book plugin no longer works (It did prior the last reboot) and
states: "No KDE adress book plugin configured yet". Why is that? It _was_
configured and now it's gone.

Further, while "Nepomuk Contact Feeder" is "Ready to index data", the "Nepomuk
EMail Feeder" reports: "System busy, indexing suspended." (My system is idle.)

I have now reconfigured the LDAP adress book, and it is working. And after
starting kontact (which puts my E-Mail-Agents into online mode) the Nepomuk
EMail Feeder switched to "Ready".

Most probably this has nothing to do with the crash reported, but I thought
better report this oddity, no matter how far fetched a connection seems, than
ignoring possibly helpful information. ;-)
Comment 27 Sebastian Trueg 2011-09-28 09:43:39 UTC
*** Bug 277513 has been marked as a duplicate of this bug. ***
Comment 28 Sebastian Trueg 2011-10-11 19:14:18 UTC
Closing this as a duplicate of bug 275880 since I am fairly certain that it can be the only source of the problem. Hopefully the patch I posted there does also solve this crash.

*** This bug has been marked as a duplicate of bug 275880 ***