[Kde-pim] Re: Frequent crashes in EntityTreeModel and other library models

[Stephen Kelly]

David Jarvie wrote:

> On Mon, November 22, 2010 12:37 pm, Stephen Kelly wrote:
>> Stephen Kelly wrote:
>>
>>> David Jarvie wrote:
>>>
>>>> When built to use Akonadi, KAlarm very frequently crashes during its
>>>> startup. Most of the crashes, which are individually non-reproducible,
>>>> occur during initialisation of the Akonadi models, including
>>>> EntityTreeModel. The majority of times, no crash dialog is displayed,
>>>> so
>>>> I can't investigate those crashes. Some crashes also occur when events
>>>> are added or removed subsequently.
>>>>
>>>> I'm quite concerned that unless things improve a lot, the Akonadi
>>>> version
>>>> of KAlarm in 4.6 will be quite unstable. I've fixed various bugs in the
>>>> KAlarm code itself, but most of the remaining crashes for which I have
>>>> traces, like the attached one, occur at a low level inside the Akonadi
>>>> models or kdeui models. As a result, they aren't easy to debug, and
>>>> suggest that the fault probably lies in the library classes rather than
>>>> in the application.
>>>>
>>>> I'd like to help fix these crashes, if somebody could tell me what else
>>>> I
>>>> can do to track them down.
>>>>
>>>> I attach a trace from the latest crash in KSelectionProxyModel /
>>>> EntityTreeModel.
>>>>
>>>
>>> I tried KAlarm today and after adding a single collection and a single
>>> item I get a crash on start up in the TemplateListModel.
>>>
>>> I don't know my way around the code, and there are a lot of singletons,
>>> which makes it hard to know where the class is actually instantiated for
>>> the first time. That makes it hard to make a minimal test case.
>>>
>>> If you can find a way to make minimal test cases the bugs can be fixed,
>>> but the current KAlarm code seems very tied together to me at the
>>> moment.
>>
>> Actually the crash I'm getting is a bug in Qt regarding the column
>> filtering that the TemplateListModel does.
>>
>> I have a unit test for it now at least.
> 
> Hi Steve,
> 
> Thanks for your response. I'll look for a few simple KAlarm configurations
> to find some which crash frequently, and post them here. Normally I tend
> to test with only a single enabled active alarm calendar, containing one
> or two alarms. Usually the alarms are recurring, since these persist after
> triggering, saving the need to re-create them frequently. That
> configuration often produces crashes on startup, but I'll look into actual
> configurations for testing.

That would help. I've just been creating alarms and collections and template 
collections (though I couldn't figure out how to put something in there) and 
archived alarms (though I couldn't figure out how to put something in 
there).

I tried inserting and removing them and couldn't make it crash.

> 
> Do you know if the Qt bug you mention is likely to be fixed soon?

Whenever it gets applied.

http://qt.gitorious.org/qt/qt/merge_requests/934

Cheers,

Steve.

> 
> Cheers,


_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/