I’ve left 5.2.0 running (and minting) for a few days on a 64 bits Windows 7 VM with 8 GB of RAM and it hasn’t crashed yet. The process uses about 3.3 GB (according to the task manager). So it doesn’t look like it’s a windows specific issue because it works fine in this VM.
There must be something else on your setup. How much memory does the process take when it’s loaded? Does it grow significantly? What’s the percentage of physical memory used (visible in the task manager)? Are you running a 64 bits Windows? Do you have other processes taking a lot of memory? What do you usually do with the client? (nothing? minting? sending transactions?)
I don’t think exchanges reported crashes recently.
This “bad alloc” error means it failed to reserve memory. The most common reason is the system is running out of memory. Either because Nu took it all, or something else did. Reporting the memory amounts would help. It may also be because the system restricts processes memory usage in some ways, but I guess you don’t have such a configuration. It may also be because the system is running out of address space (running a 32 bits version on a 64 bits system would limit the process to 4 GB of memory use, and running a 32 bits Windows would limit the whole system to 3.4 GB).
This error could suggest there’s something wrong with your block database or another database. But it’s most likely just a consequence of an earlier memory error.
