Windows command prompt out of memory and shuts down on Windows 10

[timocouckuyt]

Hi guys,

It's not really a coding issue, but I thought it would be good to try to find people who might have had the same issue and post it here.

As a test case, I tried to migrate a Gmail box with more than 50K emails over to another IMAP test box, everything runs smoothly, except the Windows CMD prompt itself. Every few hundred emails onwards, it crashes. I then rerun imapcopy with startFolderNum and startFolderMessageNum provided but it keeps on crashing every few hundred emails onwards. I'm guessing the Windows CMD prompt can't really handle of the output. Would there be a (quick) way of disabling this but still see an indication of where the script's at and what went OK or gave an error? I was thinking about writing the output to a file as a fix.

Thoughts?

// T

[timocouckuyt]

UPDATE: Logging to a file triggers the same crashing problem. What's strange tho is the crash happens on the same numbers of emails and folders. Perhaps a buffer issue?

[simialbi]

I think you gave the explanation yourself (Windows command prompt out of memory and shuts down on Windows 10).
What does your php.ini looks like? Maybe you have to disable memory_limit on cli or at least increase it.

[jozefp83]

I have a similar problem, I'm running php cli in virtual environment; the script fill the memory of system, after it's killed.
I think it's some issue with unseting memory somewhere in script; or maybe in imap class ...