Help with MemoryError

[diaphant]

Hi!
I keep getting Memory Error message while trying to convert large(>200mb) mobi files to any other format. It occurs almost immediately after start. And the error message is:

(Error Code: 1)
Traceback (most recent call last):
File "site.py", line 132, in main
File "site.py", line 109, in run_entry_point
File "site-packages\calibre\utils\ipc\worker.py", line 192, in main
File "site-packages\calibre\gui2\convert\gui_conversion.py", line 31, in gui_convert_override
File "site-packages\calibre\gui2\convert\gui_conversion.py", line 25, in gui_convert
File "site-packages\calibre\ebooks\conversion\plumber.py", line 1035, in run
File "site-packages\calibre\customize\conversion.py", line 241, in __call__
File "site-packages\calibre\ebooks\conversion\plugins\mobi_in put.py", line 33, in convert
File "site-packages\calibre\ebooks\mobi\reader\mobi6.py", line 73, in __init__
MemoryError

[eschwartz]

You will need to provide calibre with more RAM.
Make sure you are running the 64-bit version of calibre on a 64-bit OS.


How much RAM do you have, and what OS are you using?

[diaphant]

Hi.
I have 32bit windows 7, with 3.2gb RAM. And btw it's not fully used during the process.
Maybe calibre can not access some portion of my RAM? Is there any way to fix it(beside reinstalling my OS) ?

[theducks]

Originally Posted by diaphant

Hi.
I have 32bit windows 7, with 3.2gb RAM. And btw it's not fully used during the process.
Maybe calibre can not access some portion of my RAM? Is there any way to fix it(beside reinstalling my OS) ?

32 is not 64 If you have a older 32 bit processor, an OS install is a lot of pain for little gain. 3.2G is all what 32 bit Windows can use

but a 200MB Mobi? (or EPUB) is a huge file

Did it bomb immediately upon starting the conversion, or did it grind away for a bit?

Instant bomb, leads to the conclusion that the file is damaged or so odd that Calibre can not deal with it.

[cybmole]

Afaik, any single program in 32 bit windows is limited to 2gb ram, unless you install a hack override, which I recall learning how to do in order to run the half life 2 cinematic mod, ages ago. The system as a whole has only 2**32 addresses available, which is 4gb, no matter how much ram you install.

[cybmole]

http://stackoverflow.com/questions/6...erating-system

[eschwartz]

Originally Posted by diaphant

Hi.
I have 32bit windows 7, with 3.2gb RAM. And btw it's not fully used during the process.
Maybe calibre can not access some portion of my RAM? Is there any way to fix it(beside reinstalling my OS) ?

No, the problem is that 3.2 GB is simply not enough.

If you reinstall the 64-bit version of Windows -- on a 64-bit capable computer, of course -- then you can access more (lots more!) RAM (which assumes you have more RAM to use).



And calibre will try to use as much as it is allowed, but even if you have 3.2 GB a 32-bit application can't use more than 2 GB of that.
(3.2 GB is how much the OS can use, but applications have their own limits as well.)

[PeterT]

Something I *ALWAYS* wonder is why people always mention adding more RAM to Windows 64; surely it should be sufficient to ensure that the page file is allowed to grow as is needed; I'm not sure as to why RAM is needed as opposed to virtual memory.

[itimpi]

Originally Posted by PeterT

Something I *ALWAYS* wonder is why people always mention adding more RAM to Windows 64; surely it should be sufficient to ensure that the page file is allowed to grow as is needed; I'm not sure as to why RAM is needed as opposed to virtual memory.

That is because when all the RAM is being used dynamically by the same program then a swap file is not effective. It is probably something like 1000 times slower (or more) which means that program run times become unacceptable. A swap file only really works for handling memory contention between different programs, or when within a program much of the memory space ace is not being accessed so the working set can be kept in RAM.

[JSWolf]

It turns out that 8gig of ram is sufficient in most cases with a 64-bit Windows. But Calibre really does work better with the 64-bit version under a 64-bit Windows.

[BetterRed]

Originally Posted by itimpi

That is because when all the RAM is being used dynamically by the same program then a swap file is not effective. It is probably something like 1000 times slower (or more) which means that program run times become unacceptable. A swap file only really works for handling memory contention between different programs, or when within a program much of the memory space ace is not being accessed so the working set can be kept in RAM.

Thrashing (computer science) - Wikip

BR

[JSWolf]

If your system is 64-bit capable, install Windows 7 64-bit if you can. You cannot do this as an upgrade and you'll have to install all your programs again. But once done, you can install Windows 10-64 bit upgrade. Then you can install more memory to get to 8gigs.

[diaphant]

Originally Posted by theducks

but a 200MB Mobi? (or EPUB) is a huge file

Yeh, it's britannica.

Originally Posted by theducks

or did it grind away for a bit?

It does. Something like this (RAM):


What is actually bothering me, that it took less than half RAM at a time (1,6gb from 3,2gb). Why didn't it try to use 2gb at least?

But anyway, thanks guys!
I think i'll beter try calibre on some system with better RAM situation (and 64bit Windows) before digging more.

[eschwartz]

Originally Posted by PeterT

Something I *ALWAYS* wonder is why people always mention adding more RAM to Windows 64; surely it should be sufficient to ensure that the page file is allowed to grow as is needed; I'm not sure as to why RAM is needed as opposed to virtual memory.

Swapping is just really, really slow, persistent RAM.


I actually had a use for swap space recently... I was trying to compile and link a huge program that required more RAM than I have.

Really slow compile times are better than a straight-up OutOfMemoryError.
It's a pity I'd have to boot into a liveCD and repartition the swap partition, since BTRFS doesn't (yet) support swapfiles.

But you usually do not want to suffer severe speed penalties, which is why usually no one suggests it as a practical solution.

[eschwartz]

Originally Posted by JSWolf

If your system is 64-bit capable, install Windows 7 64-bit if you can. You cannot do this as an upgrade and you'll have to install all your programs again. But once done, you can install Windows 10-64 bit upgrade. Then you can install more memory to get to 8gigs.

What does this have to do with Windows 10?
Other than your entirely predictable and predictably tiresome Windows 10 proselytizing.


"you can install more memory to get to 8gigs" on Windows 7 as well.


Windows 10 is entirely orthogonal to the issue and the discussion.