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: 6
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1114 times and has 5 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
glibc detected **** free() invalid next isze (fast): 0x99149D8 ***

hello I recieved this error on my linux box. It is running gentoo 64 bit and it has all the updates. Any suggestions on the error message? boinc no loger responds after this point. Will try and restart and post outcome.
[Jul 10, 2006 5:06:23 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: glibc detected **** free() invalid next isze (fast): 0x99149D8 ***

Hi thesheff17,
We are posting errors like yours on this HPF2 thread: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=7868
We are still debugging Rosetta, so don't worry about it. When we find a work unit that causes the program to bomb, we just identify it to the staff the way that Viktors asked (Device ID #, etc.).

Lawrence
[Jul 10, 2006 6:44:10 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: glibc detected **** free() invalid next isze (fast): 0x99149D8 ***

One of my team members is reporting this identical problem:

The error I am seeing is:

*** glibc detected *** free(): invalid next size (fast): 0x09622968 ***

once per thread that dies. The last number varies.

All of these boxes are running debian stable with the new 2.6 kernel

[Jul 10, 2006 2:27:25 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: glibc detected **** free() invalid next isze (fast): 0x99149D8 ***

I removed the BOINC directory and re ran the setup script and it seems to be ok.
[Jul 11, 2006 3:10:06 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: glibc detected **** free() invalid next isze (fast): 0x99149D8 ***

Re-running the script did not work for me. I have 4 Linux boxes all getting this error and I think (?) it just started with Phase two but I could be wrong. I could not find an update on this in these forums. Anybody know anymore on this error and a possible fix?

--Thanks,
Brink
[Jul 13, 2006 5:07:42 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: glibc detected **** free() invalid next isze (fast): 0x99149D8 ***

There is no fix yet. It's a problem with the Rosetta code, and WCG are working on it (in collaboration with Baker Labs).

Restarting BOINC should download a new work unit. If not, abort it. If you are experiencing this problem too frequently, change your preferences to work only on FAAH until this is resolved.

Thank you for your patience.
[Jul 13, 2006 5:22:33 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread