Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 2
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 3923 times and has 1 reply Next Thread
DrMason
Senior Cruncher
Joined: Mar 16, 2007
Post Count: 153
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Error: rsl_malloc failed, not enough space

This is just a heads up to the devs that I got 6 errors on WUs on a machine. Most of these have had multiple computers error on them, so I'm not sure if it's the particular systems crunching, or the units themselves, or a combination.

Here is an example of the error log:
Result Name: ARP1_ 0003601_ 010_ 0--
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
The storage control block address is invalid.
(0x9) - exit code 9 (0x9)</message>
<stderr_txt>
INFO: Initializing
INFO: No state to restore. Start from the beginning.
Starting WRFMain
[15:43:16] INFO: Checkpoint taken at 2018-07-21_06:00:00
rsl_malloc failed allocating 24911668 bytes, called ..\external\RSL_LITE\rsl_bcast.c, line 270, try 1
: Not enough space
rsl_malloc failed allocating 24911668 bytes, called ..\external\RSL_LITE\rsl_bcast.c, line 270, try 2
: Not enough space
rsl_malloc failed allocating 24911668 bytes, called ..\external\RSL_LITE\rsl_bcast.c, line 270, try 3
: Not enough space

</stderr_txt>
]]>


The 6 WUs are 0022711_010; 0024337_010; 0028725_101; 0002771_010; 0006090_009; 0003601_010.
They all errored out on a Windows 10 machine with 32 gb ram, at least 710 gigs of free hard drive space (multiple drives, 710gb available on the most full drive). In the past week, 8 other ARP units have finished without issue on this same machine and the other four that I currently have on the machine seem to be crunching fine. Have crunched over 6k of ARP WUs and haven't seen this error before, so it could either be a "perfect storm" of machine weirdness or maybe something to look at with the units. biggrin

Let me know if you would like any more info. Thanks, - DrM
----------------------------------------

[May 4, 2020 4:27:07 PM]   Link   Report threatening or abusive post: please login first  Go to top 
siu77
Cruncher
Russia
Joined: Mar 12, 2012
Post Count: 22
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
confused Re: Error: rsl_malloc failed, not enough space

4 arp tasks crashed at the same time.

Here is one example:
Result Log 	

Result Name: ARP1_ 0000215_ 055_ 1--
<core_client_version>7.16.11</core_client_version>
<![CDATA[
<message>
- exit code 9 (0x9)</message>
<stderr_txt>
INFO: Initializing
INFO: No state to restore. Start from the beginning.
Starting WRFMain
[22:01:29] INFO: Checkpoint taken at 2018-10-19_06:00:00
INFO: Initializing
Starting WRFMain
INFO: Initializing
Starting WRFMain
rsl_malloc failed allocating 24911668 bytes, called ..\external\RSL_LITE\rsl_bcast.c, line 270, try 1
: Not enough space
rsl_malloc failed allocating 24911668 bytes, called ..\external\RSL_LITE\rsl_bcast.c, line 270, try 2
: Not enough space
rsl_malloc failed allocating 24911668 bytes, called ..\external\RSL_LITE\rsl_bcast.c, line 270, try 3
: Not enough space

</stderr_txt>
]]>


It seems that this happened due to a Windows update and a reboot.

Or perhaps because of a running video game ( Alien Isolation ) with not so much memory on board ( 8 GB ). Although there were no such accidents before.
[Jun 9, 2021 4:13:21 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread