Stability

[Vadim Lebedev]

Hi Ralf,

My comments are inline:

Ralf Schlatterbeck wrote:
> On Fri, Aug 01, 2008 at 11:59:35AM +0200, Vadim Lebedev wrote:
>   
>> Maybe you should try to modify QtIdle to accept CUuserProfile as 
>> constructor parameter?
>>     
>
> So far we've not observed stability problems related to QtIdle, I was
> just worried due to the comment in getUserProfile.
>
> When trying to fix the crash yesterday together with Darsha I had
> tried to modify our QtTimer to accept a CUuserProfile -- which didn't
> prevent the crash -- we get an invalid instance of a UserProfile pointer
> when calling getUserProfile on the CUuserProfile when qutecom is
> offline (we get 0xFFFFFFFF as a pointer!).
> Our fix was to destroy our QtTimer instance using
> OWSAFE_DELETE(_qtTimer);
> in QtWengoPhone::currentUserProfileWillDieEventHandlerSlot
> which fixes the crash. (This is also done for QtIdle but we overlooked
> that).
>
> I've identified two other crashes related to going offline:
> - Crash with open chat window when going offline/online:
>   - Open a chat
>   - go offline
>   - go online
>   - re-open chat to same or other contact
>   - crash
>   -> Whats the proper way to close open chat (or other?!) windows here?
>   
    I think the simplest and possibily even correct  way would be to 
close  all open chat windows.
> - Crash when clicking "Log on" when connect was recently pressed, this
>   can be reproduced if you're fast enough while the client is still busy
>   connecting:
>   - go offline
>   - in login dialog click "Connect"
>   - in qutecom menu click "Log On" while the client is still connecting
>     (you need to be quick before the connect finishes and the menu shows
>     "Log Off")
>   - crash
>   -> Probably the menu should already display "Log Off" when the connect
>      is in progress.
>
>   
    Yes, probably Connect button should generate a signal causing
    "Log On" to be disabled


> I've not yet verified these issues are present in qutecom, too (not only
> in kvats) but I'm rather positive they are. I'll now verify these and
> put them into our tracker.
>
> Vadim: Do you want an account in the kvats issue-tracker to look into
> what we're doing? I really need to investigate how we can open the
> tracker in read-only mode for the world but until this is done you can
> follow (and comment on) our issues. We have two keywords "upstream" and
> "possibly upstream" to track things we should contribute back to
> qutecom.
>
>   
Yes, i'm interested to have an account there

Thanks
Vadim



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qutecom.org/pipermail/qutecom-dev/attachments/20080801/a3f9c7b1/attachment.htm