Still seeing 'Memory Leaks.'

Example Result: 569967

<core_client_version>5.10.28</core_client_version>
<![CDATA[
<stderr_txt>
Unrecognized XML in GLOBAL_PREFS::parse_override: suspend_if_no_recent_input
Skipping: 0.000000
Skipping: /suspend_if_no_recent_input
APP: error writing checkpoint (resolving checkpoint file) -108
output_path: astronomy_checkpoint


**********
**********

Memory Leaks Detected!!!

Memory Statistics:
0 bytes in 0 Free Blocks.
778 bytes in 6 Normal Blocks.
4652 bytes in 3 CRT Blocks.
0 bytes in 0 Ignore Blocks.
0 bytes in 0 Client Blocks.
Largest number used: 5614684 bytes.
Total allocations: 5802921 bytes.

Dumping objects ->
c:\research\boinc_samples\astronomy\parameters.c(398) : {200323} normal block at 0x01A634A8, 64 bytes long.
Data: < D k ?-[ 5@> E1 44 F4 6B EB A7 E4 3F 2D 5B EB 8B 84 F2 35 40
c:\research\boinc_samples\astronomy\parameters.c(273) : {90} normal block at 0x009C6B10, 100 bytes long.
Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD
c:\research\boinc_samples\astronomy\parameters.c(263) : {87} normal block at 0x009C68E0, 512 bytes long.
Data: <1035, average > 31 30 33 35 2C 20 61 76 65 72 61 67 65 00 CD CD
{60} normal block at 0x009C52B0, 12 bytes long.
Data: <P@ E PM > 50 40 9C 00 B0 45 9C 00 50 4D 9C 00
c:\research\boinc\api\boinc_api.c(160) : {55} normal block at 0x009C2A58, 4 bytes long.
Data: < > 00 00 AD 00
c:\research\boinc\lib\parse.c(142) : {54} normal block at 0x009C29D0, 86 bytes long.
Data: < <color_scheme>T> 0A 3C 63 6F 6C 6F 72 5F 73 63 68 65 6D 65 3E 54
Object dump complete.


</stderr_txt>
]]>

---

we're loooking into this, hopefully in the next couple days we'll have a new binary out to fix the leak.

we're loooking into this...

Thanks.
As an aside, does BOINC version make a difference?

---

we're loooking into this...

Thanks.
As an aside, does BOINC version make a difference?

It looks like almost everyone across the board is getting the same leaked memory, so i'm almost positive the problem is with our code and not with BOINC :)

It looks like almost everyone across the board is getting the same leaked memory, so i'm almost positive the problem is with our code and not with BOINC :)

Beeing greedy when it comes to memory allocation is no good ;)

Here's another one (WU gs_25_1196732896_22224).
Application stopped doing anything after completeing 46,9% of WU.
Tried halting it manually from BOINC manager and restarting computations, but it failed (I'm using MS Losedows XP - this was reported earlier, as I see).

Now it's the same with gs_25_1196732896_22223 - neither it's doing anything, nor it's reporting error.

WU 884776:
<core_client_version>5.10.30</core_client_version>
<![CDATA[
<stderr_txt>
Unrecognized XML in GLOBAL_PREFS::parse_override: suspend_if_no_recent_input
Skipping: 0.000000
Skipping: /suspend_if_no_recent_input
APP: error writing checkpoint (resolving checkpoint file) -108
output_path: astronomy_checkpoint


**********
**********

Memory Leaks Detected!!!

Memory Statistics:
0 bytes in 0 Free Blocks.
778 bytes in 6 Normal Blocks.
5184 bytes in 4 CRT Blocks.
0 bytes in 0 Ignore Blocks.
0 bytes in 0 Client Blocks.
Largest number used: 5614732 bytes.
Total allocations: 5803384 bytes.

Dumping objects ->
c:\research\boinc_samples\astronomy\parameters.c(398) : {200327} normal block at 0x01A634F0, 64 bytes long.
Data: < m 8) ?^ 5@> DF 6D DE 38 29 CC D9 3F 5E BD 8A 8C 0E B8 35 40
c:\research\boinc_samples\astronomy\parameters.c(273) : {94} normal block at 0x009C6B38, 100 bytes long.
Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD
c:\research\boinc_samples\astronomy\parameters.c(263) : {87} normal block at 0x009C6908, 512 bytes long.
Data: <particle: 248, g> 70 61 72 74 69 63 6C 65 3A 20 32 34 38 2C 20 67
{60} normal block at 0x009C52F0, 12 bytes long.
Data: < @ E M > 90 40 9C 00 F0 45 9C 00 90 4D 9C 00
c:\research\boinc\api\boinc_api.c(160) : {55} normal block at 0x009C2A58, 4 bytes long.
Data: < > 00 00 AD 00
c:\research\boinc\lib\parse.c(142) : {54} normal block at 0x009C29D0, 86 bytes long.
Data: < <color_scheme>T> 0A 3C 63 6F 6C 6F 72 5F 73 63 68 65 6D 65 3E 54
Object dump complete.


</stderr_txt>
]]>

---

Here's another one (WU gs_25_1196732896_22224).
Application stopped doing anything after completeing 46,9% of WU.

Did it say 'Waiting for memory'?
I had one today (841720) that 'paused' at about 87% (Usually get around 1.96-2.02 credits @100%, errored credit of 1.74).

---

Result 1236797:

<core_client_version>5.10.30</core_client_version>
<![CDATA[
<stderr_txt>


**********
**********

Memory Leaks Detected!!!

Memory Statistics:
0 bytes in 0 Free Blocks.
94 bytes in 3 Normal Blocks.
4652 bytes in 3 CRT Blocks.
0 bytes in 0 Ignore Blocks.
0 bytes in 0 Client Blocks.
Largest number used: 4840605 bytes.
Total allocations: 5037029 bytes.

Dumping objects ->
c:\research\boinc\api\boinc_api.c(155) : {55} normal block at 0x009C2A58, 4 bytes long.
Data: < > 00 00 AD 00
c:\research\boinc\lib\parse.c(142) : {54} normal block at 0x009C29D0, 86 bytes long.
Data: < <color_scheme>T> 0A 3C 63 6F 6C 6F 72 5F 73 63 68 65 6D 65 3E 54
{47} normal block at 0x009C2958, 4 bytes long.
Data: < @ > 90 40 9C 00
Object dump complete.


</stderr_txt>
]]>

I think this was brought up in another thread, but I noticed it myself (when I've checked):
I have seen WU's reach 100% in the Boinc GUI, then appear to restart at 0.000%, continue for about 5 seconds (up to ~0.15x%), and complete.

---

Result 1236797:

5.10.30



**********
**********

Memory Leaks Detected!!!

Memory Statistics:
0 bytes in 0 Free Blocks.
94 bytes in 3 Normal Blocks.
4652 bytes in 3 CRT Blocks.
0 bytes in 0 Ignore Blocks.
0 bytes in 0 Client Blocks.
Largest number used: 4840605 bytes.
Total allocations: 5037029 bytes.

Dumping objects ->
c:researchboincapiboinc_api.c(155) : {55} normal block at 0x009C2A58, 4 bytes long.
Data: < > 00 00 AD 00
c:researchboinclibparse.c(142) : {54} normal block at 0x009C29D0, 86 bytes long.
Data: < T> 0A 3C 63 6F 6C 6F 72 5F 73 63 68 65 6D 65 3E 54
{47} normal block at 0x009C2958, 4 bytes long.
Data: < @ > 90 40 9C 00
Object dump complete.



]]>

I think this was brought up in another thread, but I noticed it myself (when I've checked):
I have seen WU's reach 100% in the Boinc GUI, then appear to restart at 0.000%, continue for about 5 seconds (up to ~0.15x%), and complete.

the reason for the WU progress going to 0% briefly is that theres a problem with the application restarting the progress when it moves from calculating the integral of the volume (which is the most computationally intensive part) to calculating the fitness using that integral and all the stars. this should be fixed in the next version.

Still getting memory leaks!

---

See also:
Results valid at all? Memory leaks everywhere?

---

Result 3438717:

Notice: Trying to get property of non-object in /export/share0/www/boinc/milkyway/html/inc/result.inc on line 79
Result ID 3438717
Name gs_201_1202477392_135386_0
Workunit 3303818
Created 7 Feb 2008 9:54:15 UTC
Sent 7 Feb 2008 10:03:06 UTC
Received 7 Feb 2008 12:11:32 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 2100
Report deadline 12 Feb 2008 10:03:06 UTC
CPU time 2534.766
stderr out

<core_client_version>5.10.30</core_client_version>
<![CDATA[
<stderr_txt>


**********
**********

Memory Leaks Detected!!!

Memory Statistics:
0 bytes in 0 Free Blocks.
94 bytes in 3 Normal Blocks.
4652 bytes in 3 CRT Blocks.
0 bytes in 0 Ignore Blocks.
0 bytes in 0 Client Blocks.
Largest number used: 6054589 bytes.
Total allocations: -1392876446 bytes.

Dumping objects ->
c:\research\boinc\api\boinc_api.c(155) : {55} normal block at 0x009C2A58, 4 bytes long.
Data: < > 00 00 AD 00
c:\research\boinc\lib\parse.c(142) : {54} normal block at 0x009C29D0, 86 bytes long.
Data: < <color_scheme>T> 0A 3C 63 6F 6C 6F 72 5F 73 63 68 65 6D 65 3E 54
{47} normal block at 0x009C2958, 4 bytes long.
Data: <P@ > 50 40 9C 00
Object dump complete.


</stderr_txt>
]]>

Validate state Initial
Claimed credit 5.45312192876877
Granted credit 6.5
application version 1.13

---