| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
DrMason
Senior Cruncher Joined: Mar 16, 2007 Post Count: 153 Status: Offline Project Badges:
|
Thanks for the info princah5, and welcome to the forums!
----------------------------------------![]() |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
princah5 said:
----------------------------------------std::bad_alloc is C++'s way to say "out of memory" and is typically thrown when failing to allocate dynamic memory on heap. Can either mean no more virtual memory (e.g. 2/4 GB Limit on 32bit or fragmented memory layout) or physcial memory limit (RAM / swap). Thanks! This device is a 2C/2T machine with a single stick of 2 GB DDR3L RAM and no swap running as close to barebones Debian 10 as possible...no desktop environment or GUI, and only BOINC-client and SSHd installed pretty much. That gives each ARP1 work unit about 1 GB of RAM to play with, but it wouldn't surprise me if the zipping/7zipping process used for file compression uses RAM not counted in the original estimates for this project, bringing me over the limit. I have a spare stick of RAM available I can throw in there, but it's not an identical stick. 1. Crucial 2 GB DDR3L...unsure of CAS timings 2. Samsung 4 GB DDR(L?)...unsure of CAS timings I could buy another stick of the Crucial...it's only $11.99 on Amazon now. Wow, RAM prices have finally come down.
[Edit 4 times, last edit by hchc at Dec 23, 2019 2:27:01 AM] |
||
|
|
|