Bug 1580262 Comment 22 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

zaggie, Thanks for clearing that up that you really have multiple (11) chimail accounts. You say only one is causing the crash? I suspect it has non-ascii or unicode folder names, right? Does comment 20 above list  all the folder for the crashing account? If not, can you reveal the names for the folders for the crashing account. If you prefer not to post them here you might consider emailing them to me.

I suspect somehow tb is choking when it goes through your folders in an attempts to replace any possible ^ with a /. But, I doubt that there are any ^'s or /'s in any of your folder names. However, it appears when it gets done checking and it terminates the string, *dst = 0, it is crashing like a buffer overrun or something.

Also, in comment 20 I dont' think the extra INBOX-X files are a big problem. Tb just uses the most recent one INBOX-5. These may be symptom of the various crashes that left the original INBOX in a corrupted state and tb created a new one. You can delete all but the highest numbered one. But even if you delete it, tb will re-download the headers and re-create it.
zaggie, Thanks for clearing that up that you really have multiple (11) chimail accounts. You say only one is causing the crash? I suspect it has non-ascii or unicode folder names, right? Does comment 20 above list  all the folder for the crashing account? If not, can you reveal the names for the folders for the crashing account. If you prefer not to post them here you might consider emailing them to me.

I suspect somehow tb is choking when it goes through your folders in an attempts to replace any possible ^ with a /. But, I doubt that there are any ^'s or /'s in any of your folder names. However, it appears when it gets done checking and it terminates the string, *dst = 0, it is crashing like a buffer overrun or something.

Also, in comment 20 I dont' think the extra INBOX-X files are a big problem. Tb just uses the most recent one, INBOX-5. These may be a symptom of the various crashes that left the original INBOX in a corrupted state and tb created a new one. You can delete all but the highest numbered one. But even if you delete it, tb will re-download the headers and re-create it.
Edit: It may also be helpful to know the character set used for your non-ascii folders. I think you can see it by right-clicking the folder and accessing Properties | Fallback text encoding.

Back to Bug 1580262 Comment 22