Crash (auto-kill) when opening a large mbox file
Ozwel opened this issue · comments
Hi,
I'm using 1.0.3.41
I can open mbox files of 200MB with no issue but when it comes to 3GB mbox files, the Mbox viewer process kills itself during the load phase (parsing archive file to create index file).
My PC is running an up to date Windows 10 Pro, I have 32GB of RAM and the CPU is an Intel i9 9900.
I can help with troubleshooting if you can suggest what to do.
Hi,
MBox Viewer should support large > 2GB mbox files when running 64 bit version. 1.0.3.40 is first UNICODE package so new bugs are possible.
Please run first mboxview.exe from ReleasePlusStackTrace folder. Please review HELP.txt what to expect when running from that folder. Apprecitae your help to investigate the issue.
It does this for me too, but it isn't dependent on size. I have some mbox files I'm trying to view and there's one that's only 5 MB that causes an instant crash when it tries to load it; meanwhile another one that's 900 MB loads fine. Not sure if I should make a new bug thread since for me it's not based on size as far as I know but it does crash in the exact same place, parsing archive file. I tried the ReleasePlusStackTrace but it did not seem to create the StackDump or MailDump TXTs when it crashed.
Thanks for reporting possibly same/similar case. The fastest way to resolve the issue would be if you could provide 5MB file to me to analyze. But that is not always possible if the file contains sensitive information. Not sure why the StackDump or MailDump TXTs files were not created. I will do quick test to make sure such file are created for basic test case.
I will consider to enhance MBox Viewer to trace parsing. That may result in very large trace file for large mbox files but it may help to understand the issue.
You could also install and run v1.0.3.39 (before port to UNICODE) and see if older version has same problem. There was very large number of code changes (and new features) to port MBox Viewer to UNICODE.
Can I assume that the name of mbox file in question has .mbox*, .eml or no extension? For some reason, file may just be ignored (unexpected format, etc ?).
Well, it appeared I could not move the mbox file to another place on my computer because of an issue with the file. So I exported the emails again to a new mbox file at another location and this time I could open with no issue.
It wasn't clear if the file was corrupted, I know my disk has no issue it's perfectly healthy. My first hypothesis is Cryptomator corrupted the file (I'm using Cryptomator at the initial location).
I guess @RingtailRaider you could check if the exported mbox files are in good shape? Are they stored in an smb share? Are you using Cryptomator or an other encryption software? Is your disk healthy?
@Ozwel I am happy you resolved the issue. MBox Viewer validates mbox files before parsing. It looks for number of fields in the email header. If fields are not found, the file is ignored. I need to consider to enhance code to report ignored files.
@RingtailRaider issue might be the same or different. It looks it is different since @RingtailRaider reported that mboxview crashes instantly. For some reason running mboxview under ReleasePlusStackTrace did not generate crash stack. I would expect Window would generate exception message upon crash. Access to problem mbox files would help to resolve the issue.
Hope you find time to provide additional information on mboxview crash. I am interested in how the crash is manifested. Typically Windows system would display exception message upon crash. Can you comment how the crash is manifested in your case?
Also I would like to provide additional information on mbox files validation. In one case mboxview will display a message when none of the mbox files under the folder is valid according to strong mboxview criteria. It will offer to the user an option to use relaxed criteria to re-verify mbox files. You can verify that the mbox file in question is ignored by the mboxview by placing only one file, i.e the file in question under some folder and select the folder from the mboxview.
Well, it appeared I could not move the mbox file to another place on my computer because of an issue with the file. So I exported the emails again to a new mbox file at another location and this time I could open with no issue.
Just wondered... did you check the length of the 'path' to the file? Some software still has problems if the overall length of the path to the root drive (C:\ or ?) is too long. In fact Windows itself has a max length of this path and can create all sorts of issues when opening files.
I usually try to move the file to a path just off the root to test the 'path issue' and eliminate this from the equation.