🚀 go-pugleaf

In article <Bx37tH.Fsu@newcastle.ac.uk> S.A.McIntyre@durham.ac.uk writes:
> I get a few screenfulls of these in my console:
> 
> 
> Nov  2 11:21:33 Workspace: window 1462 already registered
> Nov  2 11:21:33 Workspace: window 1349 already registered
> Nov  2 11:21:34 Workspace: window 1348 already registered
> Nov  2 11:21:34 Workspace: window 1347 already registered
> Nov  2 11:21:34 Workspace: window 1337 already registered
> Nov  2 11:21:34 Workspace: window 1344 already registered
> Nov  2 11:21:34 Workspace: window 1345 already registered
> Nov  2 11:21:34 Workspace: window 1343 already registered
> Nov  2 11:21:34 Workspace: window 1341 already registered
> Nov  2 11:21:34 Workspace: window 1338 already registered
> Nov  2 11:21:37 Workspace: window 1473 already registered
> Nov  2 11:21:37 Workspace: window 1472 already registered
> Nov  2 11:21:37 Workspace: window 1471 already registered
> Nov  2 11:21:37 Workspace: window 1470 already registered
> Nov  2 11:21:37 Workspace: window 1469 already registered
> Nov  2 11:21:37 Workspace: window 1468 already registered
> Nov  2 11:21:37 Workspace: window 1467 already registered
> Nov  2 11:21:37 Workspace: window 1466 already registered
> 
> 
> What's it mean and when will NeXT fix it (hah)?
> 
> Scott

Rumor has it that Engage causes this to happen (although there could  
certainly be other sources as well). 

The problem here is that what didn't used to be an "error condition" per  
se (under 2.x) is now being logged to the console. NeXTSTEP 3.0 seemed to  
ship with what I would consider to be "debugging messages" turned on. Have  
you noticed how much more activity there is in the console log than there  
was previously? Seems like every little condition in the system has a  
message associated with it.

Our product was hit by this too. The original "error condition" in the  
code wasn't so much of a problem - having a 100 messages per second being  
logged to the console (and disk!) is.

Fixes occur when developers find out about this and fix their code, or  
when NeXT turns off all these messages. What would be cool is a way to  
toggle them during product debugging. The irony is that PR2 didn't seem to  
have as many of these messages enabled as the golden 3.0 release does.  
Kind of the opposite of what you'd want.

Gordon


-- 
----------------------------------------------------------------
Gordon Van Huizen           vox: 619.488.9411  fax: 619.488.3045
Metrosoft                   gvh@metrosoft.com [NeXTmail welcome]
----------------------------------------------------------------