2011 iMac 27"/10.7.2/ATI Radeon HD 6770M

Attempting to get any project to successfully issue and complete GPU work for this host. Open discussions threads with PrimeGrid, Moo! Wrapper, Collatz -- no success so far. Addiitional issues with the core client:

1. After upgrading from 6.13.1 to 6.13.6/13.10 the GPU unit is recognized as OpenCL compatible but the client no longer requests CPU work units unless I explicitly invoke a project level "Update" request.
2. The core client size/working set has more than tripled and continues to grow -- after a few days of continuous execution the memory requirements are above 1GB.
3. The core client consumes approximately 3X cpu when compared to 6.13.1 and prior. It now idles at around 3-4% as opposed to <1%. (this is measured when the NOTICES tab is selected to minimize work unit level task reporting, obviously the cpu usage is higher when the TASKS tab is selected)

I uploaded two scenarios to the simulator and attempt to run each, both failed with a (127) error.

I can produce log files if that's required.

Thanks in advance for your assistance.
Jon

I uploaded two scenarios to the simulator and attempt to run each, both failed with a (127) error.

I don't think that the client simulator is working yet. We've just had a large BOINC server outage, expect things to fail.

I've forwarded your post to development.

---

Jon:

The client emulator should be working again now. Please create another scenario and try again. That will also help us investigate the memory usage and CPU overhead problems.

-- David

---

David:

Will do. I'll post an update when the upload and test is complete.

Thanks.
Jon

David/Jord:

The simulation (#31) appears to have completed successfully. I selected all available simulation options. Please let me know if there is anything else I can do to assist in testing or debugging.

Thanks again.
Jon

Just an update.

The core client is running at a steady state of >3.0% cpu and >1.05GB memory (Notices tab and Event Log window open). The client started at 18:10:21 CST on 7 November 2011.

Jon

Jon, can you please upload you present client_state.xml file to the client simulator and let me know? That way the developers can simulate with your file and setup what you see.

With thanks.

---

Jord, uploaded per your request -- BCE ID #32.

Please let me know if you need anything else.

Thanks.
Jon

With thanks.
Now any further increase of unexplained memory use by the client, please send in your client_state.xml file again and then post here about what you see (screen grabs are highly valued!) and where to find your state file. I'll forward all info to the developers.

---

Will do, Jord.

The behavior has been both consistent and reproducible. In fact, the client appears to have died today and I've seen similar terminations of this version since the initial install. I'll try to find some time to research the logs and post them as part of this thread.

Thanks,
Jon

Small addendum to previous post:

I looked at stderrdae.txt and stderrgui.txt for memory related error messages. Found this in stderrgui.txt:

2011-10-20 22:22:33.653 BOINCManager[163:b07] CFURLCreateWithString was passed this invalid URL string: '/System/Library/CoreServices/CommonCocoaPanels.bundle' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateWithFileSystemPath or CFURLCreateWithFileSystemPathRelativeToBase should be used instead.
SIGPIPE: write on a pipe with no reader
2011-10-29 08:46:55.328 BOINCManager[13908:b07] CFURLCreateWithString was passed this invalid URL string: '/System/Library/CoreServices/CommonCocoaPanels.bundle' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateWithFileSystemPath or CFURLCreateWithFileSystemPathRelativeToBase should be used instead.
2011-10-31 22:25:39.841 BOINCManager[166:b07] CFURLCreateWithString was passed this invalid URL string: '/System/Library/CoreServices/CommonCocoaPanels.bundle' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateWithFileSystemPath or CFURLCreateWithFileSystemPathRelativeToBase should be used instead.
BOINCManager(166,0xb0289000) malloc: *** mmap(size=16777216) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
BOINCManager(166,0xb0289000) malloc: *** mmap(size=16777216) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
ERROR: realloc() failed in MFILE::puts()
2011-11-03 20:24:16.896 BOINCManager[171:b07] CFURLCreateWithString was passed this invalid URL string: '/System/Library/CoreServices/CommonCocoaPanels.bundle' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateWithFileSystemPath or CFURLCreateWithFileSystemPathRelativeToBase should be used instead.
BOINCManager(171,0xb0103000) malloc: *** mmap(size=16777216) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
BOINCManager(171,0xb0103000) malloc: *** mmap(size=16777216) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
ERROR: realloc() failed in MFILE::puts()
SIGBUS: bus error

Crashed executable name: BOINCManager
built using BOINC library version 6.13.10
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.7.2 build 11C74
Sun Nov 6 16:01:53 2011

BOINCManager(763,0xb0103000) malloc: *** mmap(size=16777216) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
BOINCManager(763,0xb0103000) malloc: *** mmap(size=16777216) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
ERROR: realloc() failed in MFILE::puts()

--
Jon

Update:

Changed the running environment to no longer leave the core client and event log windows open (closed event log and minimized core client). While the memory usage continues to grow over time (days), it does not dramatically increase above 1GB in a matter of 3-4 days. In fact, it ran minimized for ten days -- increasing memory usage from a start-up amount of ~32MB to an ending/shutdown amount of ~350MB.

After upgrading to the 6.13.12 core client: I also did some monitoring of CPU utilization with and without the Event Log window open. It appears that the Event Log is the largest factor in CPU usage. With the primary and Event Log windows open, I continue to see 3-4% CPU utilization. Closing the Event Log window reduces the CPU utilization to <0.5%.


--
Jon