Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Sieving :
TRP_sieve wrapper crashed
Author |
Message |
|
got today an error while running TPS_sieve (Win 32 - XP SP3)
Anwendungsversion The Riesel Problem (Sieve) v1.12
The sieve process is running while the Wrapper has crashed
- exit code -529697949 (0xe06d7363)
Endstatus -529697949 (0xffffffffe06d7363)
http://www.primegrid.com/result.php?resultid=239934852
Stderr output includes debugging infos
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x7C812AFB
Had to kill the TPS_sieve process manually.
____________
Matthias
| |
|
Honza Volunteer moderator Volunteer tester Project scientist Send message
Joined: 15 Aug 05 Posts: 1957 ID: 352 Credit: 6,139,771,685 RAC: 2,272,291
                                      
|
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x7C812AFB
Low on memory?
____________
My stats | |
|
mfbabb2 Volunteer tester
 Send message
Joined: 10 Oct 08 Posts: 510 ID: 30360 Credit: 20,784,268 RAC: 731
                     
|
I got it also:
Last night 3 of my TRP sieves on the same machine error-ed out with Memory Exceptions -- the problem was the wrapper, the actual sieve task kept on running. Normal CPU no OC. Any ideas, anyone?
http://www.primegrid.com/result.php?resultid=238614102
____________
Murphy (AtP)
| |
|
|
One more result where the wrapper has crashed, but the sieve is running.
reported 3 Mar 2011 | 5:56:03 UTC
sieve killed round 3 Mar 2011 | 7:35 UTC
http://www.primegrid.com/result.php?resultid=238946562
Endstatus -529697949 (0xffffffffe06d7363)
Other machine, also Win XP 32bit SP3 3GB
____________
Matthias
| |
|
|
next one, wrapper has crashed, had to kill the TPS_sieve manually
This time Win 7 32bit.
http://www.primegrid.com/result.php?resultid=240012203
Endstatus -529697949 (0xffffffffe06d7363)
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x757C9617
____________
Matthias
| |
|
|
two more results, where the wrapper has crashed, while the TPS_sieve was running.
http://www.primegrid.com/result.php?resultid=238946564
http://www.primegrid.com/result.php?resultid=238946929
both sieve programs had a runtime with more than 7 hours when I killed them manually.
The wrapper crashed after a CPU Time 6,963.31 sec. and 843.36 sec.
____________
Matthias
| |
|
mfbabb2 Volunteer tester
 Send message
Joined: 10 Oct 08 Posts: 510 ID: 30360 Credit: 20,784,268 RAC: 731
                     
|
two more results, where the wrapper has crashed, while the TPS_sieve was running.
http://www.primegrid.com/result.php?resultid=238946564
http://www.primegrid.com/result.php?resultid=238946929
both sieve programs had a runtime with more than 7 hours when I killed them manually.
The wrapper crashed after a CPU Time 6,963.31 sec. and 843.36 sec.
Check how much disk space you have available for Boinc and how much available in general. Compare that to how much RAM your computer has. I noticed that my crashes occurred when my disk space was less than 100 MB available.
____________
Murphy (AtP)
| |
|
|
two more results, where the wrapper has crashed, while the TPS_sieve was running.
http://www.primegrid.com/result.php?resultid=238946564
http://www.primegrid.com/result.php?resultid=238946929
both sieve programs had a runtime with more than 7 hours when I killed them manually.
The wrapper crashed after a CPU Time 6,963.31 sec. and 843.36 sec.
Check how much disk space you have available for Boinc and how much available in general. Compare that to how much RAM your computer has. I noticed that my crashes occurred when my disk space was less than 100 MB available.
Hi Murphy,
On that computer I have 3 GB RAM, and more than 100 GB disk space free, boinc can use up to 10 GB disk space.
And by now, I haven't seen, that Boinc was using more than 4 GB disk space with all of my projects.
At the time where the wrapper crashed, the used RAM was less than 1.5 GB.
Additional, the wrapper uses not more than 14 MB RAM, so this should not be the problem. The TRP_sieve uses round 130 MB RAM and it doesn't crash.
We had this problem on other sub-projects before, and with a changed wrapper the problem was solved.
One point more, I did reboot that computer. After that the remaining results run without a problem. But my other projects had no crashes on the same machine. The TRP_sieve program was working fine, also without the wrapper.
The wrapper where crashing on 3 different computers, and one of this was booted (not resumed) less than a hour before the wrapper did crash. Reboot may help, but it is not the cause for the wrapper crash. I had crashes of the wrapper only on my Win 32bit computers, non on the 64bit machines.
____________
Matthias
| |
|
rroonnaalldd Volunteer developer Volunteer tester
 Send message
Joined: 3 Jul 09 Posts: 1213 ID: 42893 Credit: 34,634,263 RAC: 0
                 
|
Matthias, whats your av-solution?
____________
Best wishes. Knowledge is power. by jjwhalen
| |
|
|
two more results, where the wrapper has crashed, while the TPS_sieve was running.
http://www.primegrid.com/result.php?resultid=238946564
http://www.primegrid.com/result.php?resultid=238946929
both sieve programs had a runtime with more than 7 hours when I killed them manually.
The wrapper crashed after a CPU Time 6,963.31 sec. and 843.36 sec.
Check how much disk space you have available for Boinc and how much available in general. Compare that to how much RAM your computer has. I noticed that my crashes occurred when my disk space was less than 100 MB available.
Hi Murphy,
On that computer I have 3 GB RAM, and more than 100 GB disk space free, boinc can use up to 10 GB disk space.
And by now, I haven't seen, that Boinc was using more than 4 GB disk space with all of my projects.
At the time where the wrapper crashed, the used RAM was less than 1.5 GB.
Additional, the wrapper uses not more than 14 MB RAM, so this should not be the problem. The TRP_sieve uses round 130 MB RAM and it doesn't crash.
We had this problem on other sub-projects before, and with a changed wrapper the problem was solved.
One point more, I did reboot that computer. After that the remaining results run without a problem. But my other projects had no crashes on the same machine. The TRP_sieve program was working fine, also without the wrapper.
The wrapper where crashing on 3 different computers, and one of this was booted (not resumed) less than a hour before the wrapper did crash. Reboot may help, but it is not the cause for the wrapper crash. I had crashes of the wrapper only on my Win 32bit computers, non on the 64bit machines.
Windows! :-)
This seems a fairly sporadic event and one possibility is the depletion of the desktop heap. The other issue especially for 32-bit systems may be contiguous memory (assuming the apps need it). Sure you have a lot of virtual memory but you may not have a lot of real or contiguous memory available or the request memory was 'dirty'. | |
|
|
Hi all,
I just resumed in the 'TRP_sieve' project.
All work look similar to this one:
<core_client_version>6.12.15</core_client_version>
<![CDATA[
<stderr_txt>
BOINC sr2sieve wrapper 1.12
Using Geoffrey Reynolds' sr2sieve 1.8.10
*** Note: the wrapper is 32bit; the application that does the actual work is 64bit ***
Unrecognized XML in parse_init_data_file: userid
Skipping: 0
Skipping: /userid
Unrecognized XML in parse_init_data_file: teamid
Skipping: 0
Skipping: /teamid
Unrecognized XML in parse_init_data_file: hostid
Skipping: 144489
Skipping: /hostid
Unrecognized XML in parse_init_data_file: result_name
Skipping: TRP_sieve_1113369_0
Skipping: /result_name
Unrecognized XML in parse_init_data_file: starting_elapsed_time
Skipping: 0.000000
Skipping: /starting_elapsed_time
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1301963964.136000
Skipping: /computation_deadline
Major OS version: 6; Minor OS version: 1
pid: 152, thr: 156
.003382
(further numbers between here)
.998244
Factors file not found
called boinc_finish
</stderr_txt>
]]>
I do get Credit for those work, but not sure about the outcome for PG.
What means:
?Unrecognized XML in parse_init_data_file: computation_deadline?
What means:
?Factors file not found?
Thanks for any information !
| |
|
Neo Volunteer tester
 Send message
Joined: 28 Oct 10 Posts: 710 ID: 71509 Credit: 91,178,992 RAC: 0
                   
|
I just had the same problem all night long.
A super simple proth boinc tast took 3 hours on my machine when it only takes 7 minutes normally.
TPS_sieve for boinc/proth CPU sieve (which is excluded from my preferences) was started automatically and sucked 2 CORES at 100% for 7 hours before I caught it.
LAME.
Neo
____________
| |
|
Message boards :
Sieving :
TRP_sieve wrapper crashed |