Greetings,

My stdoutscr.txt is inundated with screensaver log entries

I was using the stable build (7.4.27) - then tried the daily build to see if the problem was fixed.

It wasn't.

I'm now running windows Vista and BOINC version 7.4.36 (x64)
Only the default logging flags are set:
File_xfer
task
sched_ops

when I installed the daily build, I used windows to uninstall BOINC first

when I installed the daily build, I did not choose the install screensaver option.

I was puzzled when checked the Windows Vista screensaver setting -
and saw the BOINC screensaver had been enabled

Before, while I was on the 7.4.27. I was able to stop the logging by changing the screen saver to the Windows floating text - something other than the BOINC screensaver.
But after I installed the daily - 7.4.36 - the BOINC screensaver was
configured (though not selected during BOINC install)
and I get 2 GB of logging in a day or two - 3 to 5 events a second logged,
and the BOINC screensaver was re-enabled over my previous choice.

Is this a known bug? Or my fault?

-edit--
The main question is: How do I turn this logging off???
-- end edit --

Temporarily, I can stop the logging by configuring a different screensaver.

T H A N K Y O U !!!
Jay

PS
I wanted to add a sample of the logs - but I lost my paste buffer.
Now, I can't reproduce the problem.
I'll reboot and try to add an example in a posting edit.

--- edit----
Here log example - while screensaver was running...

[12/22/14 13:46:47] TRACE [4736]: CScreensaver::DataManagementProc - ErrorMode = '1', ErrorCode = '82000008'
[12/22/14 13:46:47] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:47] TRACE [4736]: launch_default_screensaver C:\Program Files\BOINC\\boincscr.exe returned 0
[12/22/14 13:46:47] TRACE [4736]: CScreensaver::UpdateErrorBoxText - HRESULT '-2113929208' Updated Text 'BOINC screensaver loading'
[12/22/14 13:46:47] TRACE [4356]: CScreensaver::SaverProc Received WM_SETCURSOR
[12/22/14 13:46:47] TRACE [4296]: CScreensaver::InputActivityProc - Heartbeat.
[12/22/14 13:46:47] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:47] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:47] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:48] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:48] TRACE [4736]: CScreensaver::DataManagementProc - ErrorMode = '0', ErrorCode = '82000008'
[12/22/14 13:46:48] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:48] TRACE [4296]: CScreensaver::InputActivityProc - Heartbeat.
[12/22/14 13:46:48] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:48] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:49] TRACE [4736]: CScreensaver::DataManagementProc - ErrorMode = '0', ErrorCode = '82000008'
[12/22/14 13:46:49] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:49] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:49] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:49] TRACE [4296]: CScreensaver::InputActivityProc - Heartbeat.
[12/22/14 13:46:49] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:50] TRACE [4736]: CScreensaver::DataManagementProc - ErrorMode = '0', ErrorCode = '82000008'
[12/22/14 13:46:50] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:50] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:50] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
[12/22/14 13:46:50] TRACE [4356]: CScreensaver::SaverProc Received WM_TIMER
.... repeats every second while screensaver running ........

I don't know, perhaps try to put the <scrsave_debug> flag on in cc_config.xml?

I certainly do not have that the screen saver writes to my std*scr.txt files on 7.4.36, not with and not without that flag on. You may want to report it to the BOINC Alpha email list, to see if others there see that as well.

In the mean time, do manually delete the file before starting BOINC.

---

I asked the developers to look into this. They are checking things if only to figure out why the std*.txt files refuse to change over to a new version of themselves when they hit 2MB sizes. One of the developers found his stdoutscr.txt file to be 141MB.

For comparisons, mine is just 141KB.

Anyone else checking, please see the file size of stdoutscr.txt in C:\users\{your name}\appdata\roaming\BOINC\
These files in the data directory are no longer updated.

---

Thanks Jord!!!

Jay

I did experiment with setting the <scrsave_debug> flag.

with scrsave_debug = 1 ( set by "BOINC Diagnostic Log Flags" and verified in cc_config.xml
and screensaver active - the bulk of the logs entries are like:

[12/29/14 15:10:33] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:33] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:33] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:34] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:34] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:34] TRACE [3928]: CScreensaver::InputActivityProc - Heartbeat.
[12/29/14 15:10:34] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:34] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:35] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:35] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:35] TRACE [1464]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 15:10:35] TRACE [3928]: CScreensaver::InputActivityProc - Heartbeat.

947 KB in about an hour


I tried turning the flag back off; looking at the logs;
turning the flag on and looking again..

The logs did not stop.
The number of messages between heartbeats increased and an error code started.

[12/29/14 17:43:43] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:43] TRACE [856]: CScreensaver::InputActivityProc - Heartbeat.
[12/29/14 17:43:43] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:43] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:43] TRACE [1352]: CScreensaver::DataManagementProc - ErrorMode = '0', ErrorCode = '82000008'
[12/29/14 17:43:43] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:44] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:44] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:44] TRACE [856]: CScreensaver::InputActivityProc - Heartbeat.
[12/29/14 17:43:44] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:44] TRACE [1352]: CScreensaver::DataManagementProc - ErrorMode = '0', ErrorCode = '82000008'
[12/29/14 17:43:44] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:45] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:45] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER
[12/29/14 17:43:45] TRACE [1352]: CScreensaver::DataManagementProc - ErrorMode = '0', ErrorCode = '82000008'
[12/29/14 17:43:45] TRACE [856]: CScreensaver::InputActivityProc - Heartbeat.
[12/29/14 17:43:45] TRACE [1280]: CScreensaver::SaverProc Received WM_TIMER

Hope this may help..

Thanks again,

Jay

A fix for this problem is forthcoming. It'll be in a next BOINC version.

LIB: We do not need to log trace statements on release builds (MSVC only).
LIB: Reset the file buffer size to 0 after cycling the stderr log file.

Source

---