Ticket #306 (assigned Defect)

Opened 1 year ago

Last modified 2 months ago

Missing messages in GUI

Reported by: KSMarksPsych Assigned to: romw (accepted)
Priority: Major Milestone: 6.4
Component: Manager Version:
Keywords: Cc: Pepo

Description

First reported here, and a second report in the same thread, here.

There seem to be large gaps with missing messages in the message window/tab of the GUI but all messages appear in stdoutdae.txt.

Reported as happening on both 5.10.7 and 5.10.8.

Change History

(in reply to: ↑ description ) 07/04/07 09:53:34 changed by WHRoeder

Replying to KSMarksPsych:
Here's the 5.10.8 logs.
GUI lines 54-57: 

7/3/2007 10:35:51 PM|SETI@home|Restarting task 26fe00aa.9890.19122.704808.3.122_0 using setiathome_enhanced version 515
7/3/2007 10:35:51 PM||[cpu_sched_debug] enforce_schedule: end
7/4/2007 6:52:09 AM||[cpu_sched_debug] finished preempt loop, nrunning 1
7/4/2007 6:52:09 AM|Einstein@Home|[cpu_sched_debug] h1_0429.05_S5R2__82_S5R2c_0 sched state 1 next 1 task state 0


stdoutdae.txt lines 3659-3663 

2007-07-03 22:35:51 [SETI@home] Restarting task 26fe00aa.9890.19122.704808.3.122_0 using setiathome_enhanced version 515
2007-07-03 22:35:51 [---] [cpu_sched_debug] enforce_schedule: end
2007-07-03 22:36:51 [---] [cpu_sched_debug] enforce_schedule(): start
2007-07-03 22:36:51 [SETI@home] [cpu_sched_debug] want to run: 26fe00aa.9890.19122.704808.3.122_0


stdoutdae.txt lines 8307-8314 

2007-07-04 06:51:09 [SETI@home] [cpu_sched_debug] 26fe00aa.9890.19122.704808.3.127_1 sched state 2 next 2 task state 1
2007-07-04 06:51:09 [---] [cpu_sched_debug] enforce_schedule: end
2007-07-04 06:52:09 [---] [cpu_sched_debug] enforce_schedule(): start
2007-07-04 06:52:09 [SETI@home] [cpu_sched_debug] want to run: 26fe00aa.9890.19122.704808.3.127_1
2007-07-04 06:52:09 [SETI@home] [cpu_sched_debug] processing 26fe00aa.9890.19122.704808.3.127_1
2007-07-04 06:52:09 [SETI@home] [cpu_sched_debug] 26fe00aa.9890.19122.704808.3.127_1 is already running
2007-07-04 06:52:09 [---] [cpu_sched_debug] finished preempt loop, nrunning 1
2007-07-04 06:52:09 [Einstein@Home] [cpu_sched_debug] h1_0429.05_S5R2__82_S5R2c_0 sched state 1 next 1 task state 0

(in reply to: ↑ description ) 07/17/07 05:51:11 changed by WHRoeder

Reported as happening on both 5.10.7 and 5.10.8.

5.10.13 also

11/17/07 05:16:49 changed by Didactylos

Please attach large logs as files. Deleted comment is reproduced here: --- 08/22/07 19:54:33 changed by Barbud

I was the original complainer about this message some time ago. I only noticed it because I am doing alpha testing sometimes and I would leave the computer for a few days. When I come back to look back on the messages via the GUI I noticed large chunks of time were missing. I would then have to go directly to the stdoutdae file to see if there any errors.

This pc used to be a high end gaming pc now it just runs BOINC.
Intel E6700 processor, waiting for the wife to say ok to buy the quad.
4Gig Ram
WINXP Home
BOINC 5.10.13

I have copied the entire contents of the GUI messages tab. Sorry it is so long and I am not sure how to make the scroll bar for the code block smaller. As you can see by scanning thru the dates there are large blocks missing. Now if I go into the stdoutdae file everything is there except for some of the first entries in the GUI messages are not int the stdoutdae. Below are the first entries in the stdoutdae.txt but if you look in the next block these are not even listed in the GUI messages tab. First lines from stdoutdae.txt 

2007-08-17 15:57:16 [The Lattice Project] [file_xfer] Finished upload of file 224482590.9780102250632569.23_2_3
2007-08-17 15:57:16 [The Lattice Project] [file_xfer] Throughput 4074 bytes/sec

BOINC 5.10.13 GUI messages

<snip massive log>

This is repeatable. I can send files to anybody that wants to look closer. Please advise. Again sorry that this message is so long.

Thanks for the assistance.

05/15/08 18:24:58 changed by Pepo

  • cc set to Pepo.

06/24/08 12:14:29 changed by Didactylos

  • priority changed from Minor to Major.
  • milestone changed from Undetermined to 6.2.

Explanation by Rom (from boinc_alpha):

After 20 minutes or so Windows shuts down the timers the manager uses to maintain state, so it stops getting the latest message updates. The CC only retains the last 1000 messages in memory, so when a bunch of log flags are turned on that buffer gets cycled through really quickly. When the manager wakes back up it requests all the latest messages and gets back the last 1000, and anything before that is forgotten.

06/24/08 13:59:43 changed by romw

  • status changed from new to assigned.
  • milestone changed from 6.2 to 6.4.

This will be resolved with the changes related to the RPC Thread in the 6.4 release.

06/24/08 14:00:48 changed by romw

I should also point out that this bug has been around since 06/2006.

06/30/08 10:39:59 changed by romw

Updated from last message received about issue.

-----Original Message----- From: David Anderson davea@ssl.berkeley.edu Sent: Tuesday, June 24, 2008 1:19 PM To: Rom Walton Cc: Jorden van der Elst; Charlie Fenton Subject: Re: [boinc_alpha] BOINC 6.2.8 released for Windows The bottom line is: - we need to poll for messages no matter what tab is open - we need to use something other than WM_TIMER. Let's defer this until we put in the GUI RPC thread (and let's get started with that ASAP) -- David

If this page is incomplete or incorrect, please edit it or add it to the wiki to-do list. To do this, you must be logged in; click Login or Register above.