[issue38923] Spurious OSError "Not enough memory resources" when allocating memory using multiprocessing.RawArray

Brian Kardon added the comment: Ah, thank you so much! That makes sense. I'll have to switch to 64-bit python. I've marked this as closed - hope that's the right thing to do here. -- resolution: -> not a bug stage: -> resolved status: open -> closed

[issue38923] Spurious OSError "Not enough memory resources" when allocating memory using multiprocessing.RawArray

Christian Heimes added the comment: Good catch, Zach! A 32bit version of Python would certainly explain your problem. A 32bit process can only address 4 GB of address space. Almost half of the address space is reserved for OS, stack, Python itself, and other things. That leaves a little

[issue38923] Spurious OSError "Not enough memory resources" when allocating memory using multiprocessing.RawArray

Zachary Ware added the comment: You appear to be using a 32-bit version of Python on Windows; do you get the same behavior using the 64-bit version? -- components: -ctypes ___ Python tracker

[issue38923] Spurious OSError "Not enough memory resources" when allocating memory using multiprocessing.RawArray

New submission from Brian Kardon : When I try to create a series of multiprocessing.RawArray objects, I get an "OSError: Not enough memory resources are available to process this command". However, by my calculations, the total amount of memory I'm trying to allocate is just about 1 GB, and