Le 12-10-13 18:30, Mailing a écrit :
Hi Wolfgang,
Hi Sebastian,
creating a new empty mailbox is working fine with the nightly build. What was the root cause of the issue?
Technically, a non-talloc pointer that was passed to talloc_realloc for reallocation. This did not happen before because we were copying data in order to return a talloc-made pointer, but copy operations are heavy, especially when performed on large chunks. This is the kind of errors that occurs often during optimisations.
I did fixe another case related to this before 2.0.1 but that one never showed in my environment before the release, unfortunately.
Now I try to import an existing mailbox, but this is giving me also an samba panic crash. For me it looks like Openchange IMAP is trying to pare a message. Do you have a hint how to find out what is wrong here? Oct 13 23:58:48 samba [25717]: <MAPIStoreMailMessage:0x3e524b8:3023.eml> -dealloc Oct 13 23:58:48 samba [25717]: <MAPIStoreMailMessage:0x3ded6d8:(null)> -init Oct 13 23:58:48 samba [25717]: <MAPIStoreMailMessage:0x3ded6d8:3024.eml> -dealloc Oct 13 23:58:48 samba [25717]: <MAPIStoreMailMessage:0x3d07a68:(null)> -init Oct 13 23:58:48 samba [25717]: <MAPIStoreMailMessage:0x3d07a68:3025.eml> -dealloc Oct 13 23:58:48 samba [25717]: <MAPIStoreMailMessage:0x272d8a8:(null)> -init Oct 13 23:58:48 samba [25717]: <MAPIStoreMailMessage:0x237a968:(null)> -init /usr/sbin/samba: Uncaught exception NSInvalidArgumentException, reason: Tried to add nil to set
That is an interesting bug, because it is as if one of the messages parsed above did not have a body. This is possible but very rare.
The fix is quite simple, I will commit it tomorrow when at work. Wolfgang -- [email protected] https://inverse.ca/sogo/lists
