Message boards : Questions and problems : 7.0.28 (x86) Screen Saver Problem
Message board moderation
Author | Message |
---|---|
Send message Joined: 29 Jul 12 Posts: 5 ![]() |
Hello; The screen saver kicks in and I terminate it via mouse movement or keystrokes. I follow up termination with a quick view in Procexp.exe from sysinternals and the boinc.scr files is remaining in my tasklist and still consumes ticks from the CPU. I noticed this was an issue in the past in 2009 from a search in the forum. Windows XP Pro SP3 (x86) |
Send message Joined: 29 Jul 12 Posts: 5 ![]() |
Whoops; perhaps I should mention this only occurs when clicking "preview" in display settings. The screen saver does appear to function just fine when it is fired following the timeout. |
![]() Send message Joined: 29 Aug 05 Posts: 15634 ![]() |
Repeatable with Windows 7, so forwarded to development. Albeit, I suspect this is a Windows bug. It's their preview function that doesn't work correctly. |
Send message Joined: 29 Jul 12 Posts: 5 ![]() |
Thank you; I must add that the behavior is now occuring when the screen saver fires after the timeout. I'm participating in POEM@Home and Docking. I'm left with two processes both boinc.scr. One is consuming no ticks and the other is consuming <= 50%. |
![]() Send message Joined: 29 Aug 05 Posts: 15634 ![]() |
The developers finally had time to look at this, and put in a fix. It will be fixed in BOINC 7.0.34 WINSCR: Fix problem with the screensaver needlessly cycling in preview mode. Ugh. |
Send message Joined: 29 Jul 12 Posts: 5 ![]() |
Its me again... and now I'm using Windows 7 x64. And... I noticed the problem again. ;) Einstein@home. The screen saver is firing off the system timer and the boinc.scr is remaining resident and using .05 CPU%. Did the previous patch make it into version... 7.0.28 (x64)? |
Send message Joined: 29 Jul 12 Posts: 5 ![]() |
Whoops, i guess not. haha. I should read the thread before posting. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.