Summary: | kaddressbook crashes when moving mails twice | ||
---|---|---|---|
Product: | [Applications] kaddressbook | Reporter: | Jan Essert <netz> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | tokoe |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jan Essert
2010-04-19 19:15:42 UTC
Hej Jan, you copied mails inside KAddressBook? What was the output on the console when this crash happened? Ciao, Tobias I copied mails inside kaddressbook from one folder to another folder in the same akonadi resource. I did not start it from a console, so I have no output. After restarting kaddressbook, my contacts were successfully copied, as far as I can see, none were lost. I can try again from the console. I have managed to reproduce the crash by moving large amounts of contacts around. Simply copying things twice does not seem to be enough. The total console output was: kaddressbook(23525)/libakonadi Akonadi::EntityTreeModelPrivate::monitoredItemChanged: Got a stale notification for an item which was already removed. 1181 "b1170" leskaddressbook(23525)/libakonadi Akonadi::EntityTreeModelPrivate::monitoredItemChanged: Got a stale notification for an item which was already removed. 1041 "b1000" Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc KCrash: Application 'kaddressbook' crashing... sock_file=/home/jan/.kde4/socket-baldur/kdeinit4__0 I think that the first two "stale notification"-messages were well before the crash. *** This bug has been marked as a duplicate of bug 213468 *** |