Crash when using keybinding to move to another mailbox

Do you still have this issue with the latest test release? I don't seem to be able to reproduce it.

If you can, does it happen every time you hit n or only some times?

(I have seen somewhat similar crashes reported, but I've not been able to reproduce any of them.)

I can no longer reproduce it. It was reproducible for about 8-10 hours (and every single time I hit 'n'), but then it stopped. No idea what the stopping correlated with. It was not because I updated MM.

But now gone to MM 5566, and will update if I see anything.

This has started happening again. I've sent the crash reporting. Any other digging I can do?

Does it happen if you reduce it to selectNextCountedMailbox:?

Does it matter which mailbox is selected and what the next mailbox is?

(Looking for triggers since this would be much easier to fix if I can reproduce it.)

1. I think that when I first played with it, reducing to selectNextcountedMailbox did not make a difference. But don't act on that, I can't be 100% sure.

2. It definitely did not matter which mailbox was selected and which was the next one.

3. Although this happened several times in a row, I just continued using, and now I can no longer reproduce. Whatever this is, it is very very specific. I think now I'm aware enough about how specific at is that next time I can try to pin it down more... (at least I'm removing possible situations..) Sorry.

OK. I reloaded MailMate from backup, and can reproduce.

The fault is with: "setFilterKey:", "unread".

I've included an image, to explain. The crash happen when setFilterKey, unread (with no selectNextCountedMailbox) is used on the box "Mailing Lists." This is an empty box, which simply contains smart mailboxes. [I don't know why I did it this way, instead of another smart mailbox, but anyway].

In fact, I'm not sure how I got it to show up with a folder icon, not the smart mailbox icon. In fact, it seems to be a smart mailbox, defined like this:

{ countKey = "none"; filter = "(#flags.flag = 'ListServs' and #flags.flag !=[x] '\Seen')"; name = "Mailing Lists"; parentUUID = "DCE5A74E-D001-4561-B3CA-1DA311C5EE5F"; uuid = "A6060EA5-56AC-46EB-A272-4CDFA46CB44E"; },

Here are some relevant conditions:

Crash happens 1) whether or not there are unread messages in the smart sub-mailboxes. 2) whether or not there is a displayed count on the mailbox. 3) the crash does NOT happen for the parent "Mailboxes" mailbox. 4) The crash still happen even when I remove all smart-sub-mailboxes. 5) still happen when I move the box from it's current location to another (even if I quite first, re-open and then try).

I can overcome this problem very easily, now that I know what it is. I can simply switch the parent mailbox. Perhaps not a problem really worth pursuing, but FYI, that's what I found. If you'd like to me to check anything else, I can. But no worries if not.

ah, the image.

Of course, I should add that this behavior disappeared for some reason, which was not a redefinition of mailboxes on my part. I'll keep the box around just to see if I can spot when the problem disappears.

Hmm, I'm not getting the same crash type as you originally added to this ticket, but I am getting a crash related to setFilterKey:. Just to make clear that there just might be 2 issues.