close
Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Opened 6 months ago

Closed 2 months ago

#554 closed bug (worksforme)

ClearFolderMails crash

Reported by: Elwood Owned by:
Priority: normal Milestone: YAM 2.10
Component: mail indexing Version: nightly build
Severity: major Keywords:
Cc: OS Platform: AmigaOS4
Blocked By: Blocking:
Release Notes:

Description

Summary

There was an email edit window opened in the background. I was doing something else on another program. At some point, the Grimreaper opened on the foreground.

Maybe Yam was saving the edited email when the crash occured.

Steps to reproduce

Unknown

Expected results

Actual results

Regression

Notes

Yam automatic update reports nothing to update so I have all later versions (Yam, MUI, codesetslib).

Full crashlog attached.

Attachments (1)

Crashlog_YAM_2014-04-28_22-23-58.txt (29.8 KB) - added by Elwood 6 months ago.
crashlog

Download all attachments as: .zip

Change History (12)

comment:1 follow-up: Changed 45 years ago by Elwood

  • Status changed from pending to new

comment:2 follow-up: Changed 45 years ago by Elwood

  • Status changed from pending to new

Changed 6 months ago by Elwood

crashlog

comment:1 follow-up: Changed 6 months ago by tboeckel

  • OS Platform changed from undefined to AmigaOS4
  • Priority changed from undecided to normal

Which version of YAM are you using? YAM 2.9p1 or 2.10-dev? No pending updates does not tell anything about the used version.

Then try to reproduce this issue using the corresponding debug build and create a FOLDER log with it. All I can tell from the crashlog is that it happened while YAM was flushing the folder index automaically after the usual timeout. If it is not reproducable it is unlikely we will be able to fix this issue.

comment:2 in reply to: ↑ 1 ; follow-up: Changed 6 months ago by Elwood

Replying to tboeckel:

Which version of YAM are you using? YAM 2.9p1 or 2.10-dev?

I selected "Version : nightly build" ;-) so 2.10-dev 27.04.2014

I just hoped the offset in the crashlog could ring a bell :-/

comment:3 in reply to: ↑ 2 Changed 6 months ago by tboeckel

Replying to Elwood:

Replying to tboeckel:

Which version of YAM are you using? YAM 2.9p1 or 2.10-dev?

I selected "Version : nightly build" ;-) so 2.10-dev 27.04.2014

I know, but in general there is nothing like "the one nightly build" but lots of them instead. Hence we need to know the exact date. If you are using an older nightly build it might be possible that the bug has been fixed in the mean time already.

I just hoped the offset in the crashlog could ring a bell :-/

Unfortunately not. I think Jens should not strip the binaries for the nightly builds. Then we are able to get more detailed information from the crashlog.

But as I said already, if possible please try to reproduce this issue using the debug version and create a FOLDER log. That should contain more suitable information.

comment:4 Changed 6 months ago by tboeckel

  • Status changed from new to pending

comment:5 follow-up: Changed 6 months ago by Elwood

Hi,

Even if I didn't have another crash, I switched to debug version and updated to nightly build 07/05/2014

Leaving Yam opened with an email being edited, I see this debug output:
00: D: DockyIcon.c:213:remove Docky icon
00: D: DockyIcon.c:242:Docky icon changed
00:W: MailList.c:457:FreeMail attempt on mail (58330f18 ) with RefCounter > 0 (1)
00:W: Timer.c:891:timer event received but no timer was processed!!!

Not necessarily a problem but I see 2 things that could indicate some problem:

  • it talks about a Docky but I have none in Amidock.
  • the last line could indicate something wrong in the use of the timer device.

comment:6 in reply to: ↑ 5 Changed 6 months ago by tboeckel

Replying to Elwood:

  • it talks about a Docky but I have none in Amidock.

The message about the removed docky icon just indicates that no docky icon is configured. Updating the AppIcon will also update the docky icon, no matter if it is used or not.

  • the last line could indicate something wrong in the use of the timer device.

It may happen that YAM receives a signal to handle a timer event but actually handles two events at a time. The signal will still be pending and next next timer handling will do nothing and cause the warning. Nothing harmful.

Better concentrate on finding a reproducable test case for this ticket's issue than jumping to conclusions about completely unrelated stuff.

comment:7 Changed 2 months ago by tboeckel

  • Status changed from new to pending

Any news on this issue?

comment:8 Changed 2 months ago by Elwood

No. I didn't have it again.

comment:9 Changed 2 months ago by tboeckel

  • Milestone set to YAM 2.10
  • Resolution set to worksforme
  • Status changed from new to closed

Please reopen this ticket if it happens again.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

  • Philippe Ferrucci(Reporter, Participant)