New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MemoryError on large restore #42
Comments
I restored multiple times my 30000 emails without any problems on Mac OSX, Linux (and few times on windows). |
Let me know if there's anything I can do to help! |
@Halu I need to profile the program and it will take some time. |
Perhaps another hint at what is going wrong: when continueing using the --restart option, gmvault fails within the first 50 emails, again with the same MemoryError, as if it buffers all the emails it already has restored anyway. Restarting the gmvault-shell has no effect. |
Ok thanks, I don't understand your problem but I am profiling Gmvault to remove memory fragmentation issues. Thanks, Guillaume |
Sure, I'll be happy to help testing. Thanks for the quick responses! |
@Halu I have prepared v1.6-dev available from here http://bit.ly/JtfbvD. If it fails again send me by email guillaume((dot))aubert((at))gmail((dot))com the log file that should be under C:\Users\MyUser and called gmvault.log. Please zip it before to send it if it is big. Waiting for your results now. Many thanks for your help. |
@Halu Did you have time to do a test ? I will close the issue in the mean time because other people could test the fix for me. |
It did not work alas, it failed on one specific email which I sent you as an email attachment to you 6 days ago :) It is unclear to me though if it still is a memory issue or that I'm encountering another bug... |
@Halu Ooups yes sorry. Just to be sure. Now it doesn't eat all your memory but fails for one email. There is something in your email that is special and I need to analyse it (probably a special char but I need to understand who did put it). |
Deleting the 'faulty' .eml.gz/meta-files does help, it indeed continues the restore when I retry after deleting. However, even though the hanging does not eat my memory anymore, I noticed that the gmv_cmd.exe does hog the CPU: it keeps at a steady 50% on my dualcore cpu while it hangs, which makes me think the hanging on certain emails may somehow still be related to the previous memory errors, except that the memory is now not eaten anymore :) I'll continue restoring now whilst deleting those few mails that give raise to trouble, as it is a fine workaround. |
@Halu If the emails are not confidential please consider sending them to me. I will make a test suite with them. |
v1.6beta, OSX 10.6, I'm getting this issue too. Got up to 22GB of virtual memory then the Mac freezes totally as it runs out of hard drive space. If I delete/move the problematic email, is there an easy way for me to set the upload going again from the failed point? Is there any danger of creating duplicates? |
Hi, I am working on that issue but sometimes emails contain "crap" and they do Thanks, On Wed, Jun 13, 2012 at 11:09 PM, bommy <
|
Thank you. How would I identify and open the email to see if it's anything Screenshot of the failure state attached. I'm actually trying to re-do the Tom On 14 June 2012 08:01, Guillaume Aubert <
|
Sorry, attachment bounced, uploaded here - http://bit.ly/tomwhitakerpublic Tom ---------- Forwarded message ---------- Thank you. How would I identify and open the email to see if it's anything Screenshot of the failure state attached. I'm actually trying to re-do the Tom On 14 June 2012 08:01, Guillaume Aubert <
|
@bommy. What operation were you doing ? sync or restore ? |
It was a restore, thanks @gaubert. |
@bommy so you should have the email id in the logs of Gmvault. It is the last message that has been restored. For example The id here is 1293213852590002613 after in the terminal of your mac, you can do: Move the files to quarantine: Then the email is 1293213852590002613.eml.gz Thanks for the help. |
I am having the MemoryError problem as well while trying to restore a large mailbox. The restore will work for awhile and then I will get this: Restore email with id 1354135464925655217. === Exception traceback === === End of Exception traceback === If i use the --restart switch it will work for awhile again, but after about a half hour it will fail with the MemoryError. I've been trying to restore this mailbox for 2 days and I am now getting a lot of heat for it not being done. Please advise on what I should do. Thanks |
@3formit What version are you using ? v1.6-beta ? |
Correct 1.6 beta |
@3formit I have version 1.7 in alpha available here: http://bit.ly/JtfbvD. |
@3formit did you have time to try it and was it better with 1.70alpha. Thanks, |
After restoring the first 19050 emails to a new gmail address (migrating from an old one), I received the following exception (win7 x64, 6gb ram, gmvault 1.5-beta):
Restore email with id 1319881181591886388.
Error: .
=== Exception traceback ===
Traceback (most recent call last):
File "gmv_cmd.py", line 515, in run
File "gmv_cmd.py", line 423, in _restore
File "gmvault.pyc", line 1032, in restore
MemoryError
=== End of Exception traceback ===
When retrying, it raised the same exception after restoring only 6550 mails. I already tried to see if it possible to adjust the amount of reserved memory for python application (as it is possible for Java for example), but apparently there is no such option as Python's memory manager takes care of that.
I haven't done any Python coding myself, but my first guess at a fix would be that some resources need to be freed after a successful iteration of the for-loop starting at line 960 of gmvault.py...
The text was updated successfully, but these errors were encountered: