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: 146
Posts: 146   Pages: 15   [ Previous Page | 1 2 3 4 5 6 7 8 9 10 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 9312 times and has 145 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: An OSX bug

I am trying one thing, under my processor preferences I unchecked "Allow Nap". I've noticed it gets checked without my doing. Wondering if that might be the problem.

This didn't work. I saw in boincview that one of my FAAH units was yellow, meaning low cpu efficiency and the "Allow Nap" was unchecked. Back to the drawing board... sad
[Jul 23, 2007 5:09:02 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: An OSX bug

Just bumping this thread up since it's still a problem.
Now I'm on OSX 10.5 and tried every version up to the latest version of boinc, now 5.10.29, with no luck. Any idea's...anyone? thinking
[Nov 11, 2007 9:03:23 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Bearcat
Master Cruncher
USA
Joined: Jan 6, 2007
Post Count: 2803
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: An OSX bug

I stopped crunching until this gets resolved. Seems to only do this on mac pro's. My mini never had this problem. I tried different things and think it has something to do with the hard drives falling to sleep. I uncheck put hard drives to sleep but do catch them going to sleep anyway. I'll keep checking here to see if this got resolved but won't crunch until its fixed.
Randy
----------------------------------------
Crunching for humanity since 2007!

[Nov 12, 2007 11:17:22 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: An OSX bug

I noticed one of my work units again stalled and I went looking for any kind of errors and found this on the OSX console screen...

11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray process with PGID equal to this dead job: PID 650 PPID 99 wcg_dddt_autodoc
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray process with PGID equal to this dead job: PID 103 PPID 99 wcg_dddt_autodoc
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray process with PGID equal to this dead job: PID 99 PPID 1 boinc
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray zombie process with PGID equal to this dead job: PID 651 PPID 650 ps
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray zombie process with PGID equal to this dead job: PID 104 PPID 103 ps
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Exited: Terminated
11/12/07 6:40:30 PM [0x0-0x13013].edu.berkeley.boinc[698] Using wxWidgets 2.6.3.

Does this mean anything to you developer types??
[Nov 13, 2007 4:52:38 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: An OSX bug

I noticed one of my work units again stalled and I went looking for any kind of errors and found this on the OSX console screen...

11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray process with PGID equal to this dead job: PID 650 PPID 99 wcg_dddt_autodoc
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray process with PGID equal to this dead job: PID 103 PPID 99 wcg_dddt_autodoc
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray process with PGID equal to this dead job: PID 99 PPID 1 boinc
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray zombie process with PGID equal to this dead job: PID 651 PPID 650 ps
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Stray zombie process with PGID equal to this dead job: PID 104 PPID 103 ps
11/12/07 6:40:13 PM com.apple.launchd[78] ([0x0-0xa00a].edu.berkeley.boinc[97]) Exited: Terminated
11/12/07 6:40:30 PM [0x0-0x13013].edu.berkeley.boinc[698] Using wxWidgets 2.6.3.

Does this mean anything to you developer types??

Yup, just to confirm that this message is created every time a work unit hangs. It did it again a few minutes ago and got the same type of message.
Anyone got any idea's why this is happening? anyone...anyone...Bueller...Bueller
[Nov 14, 2007 4:42:15 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: An OSX bug

I have not had the "daily" work unit freeze for 3 or 4 days now. I upgraded to boinc 5.10.30 but at the same time I updated my mac to 10.5.1.
So I don't know what actually stopped the freeze-ups, the boinc or OSX update/upgrade...?
I will monitor to see if the freeze-up occurs again.

Bearcat, have you seen any change?
[Nov 19, 2007 12:36:08 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Bearcat
Master Cruncher
USA
Joined: Jan 6, 2007
Post Count: 2803
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: An OSX bug

I stopped crunching until the bug got fixed. I will download the new version and start again and see what happens.
Randy
----------------------------------------
Crunching for humanity since 2007!

[Nov 19, 2007 3:07:00 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Bearcat
Master Cruncher
USA
Joined: Jan 6, 2007
Post Count: 2803
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: An OSX bug

Downloaded the latest version. 17 minutes into crunching, 1 WU locked up. Had to shut down boinc and restart. Ran the rest of the night with no problems. Downloaded 1 more set of WU's and will see if it happens again. Am running with the updated 10.5.1 also.
Randy
----------------------------------------
Crunching for humanity since 2007!

[Nov 19, 2007 2:22:05 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: An OSX bug

I pointed this thread out to Charlie Fenton, the BOINC Mac developer.

He had a number of thoughts, but wasn't able to come to a firm conclusion. He did suggest that it might be a similar problem to one encountered by Einstein@home.

If you want to help debug this further, he says:

>There are a number of tools for debugging this:
> - use ps from the command line with the -M option to view the cpu time
> of each thread.
> - use /Applications/Utilities/Activity monitor to view the application's
> CPU usage
> - use Shark (installed with the CHUD tools from the OS X install DVD to
> get a stack trace of each thread and see where it is spending its time
> - attach to the application with gdb when the application is hung
[Nov 19, 2007 5:24:17 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: An OSX bug

Well, it hung again.
If I start debugging this where am I going to send the debug data. I can't post it here, it's too big. Does this boinc mac developer have an email address where I can send this data?
[Nov 20, 2007 1:05:06 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 146   Pages: 15   [ Previous Page | 1 2 3 4 5 6 7 8 9 10 | Next Page ]
[ Jump to Last Post ]
Post new Thread