..or try the latest Neo 2.1 EA test patch. I merged my Neo 2.0 AB3 changes into the test patch (Test Patch 5) that I posted about 7 hours ago in bug 2202.
This combination of 2.1 EA and patches causes a new (mis)behaviour.
I open an existing document. I print it (no editing at all). I close it by clicking on the red traffic light.
The document seems to have closed but I am left with an 'empty' white window.
All subsequent commands in Neo produce no response. I have to force quit but on re-starting there is no recovery suggesting that the document was indeed closed properly.
(I'm going to have to restore this user's computer to some semblance of normal functionality by Monday morning latest.) _________________ Ray Saunders
World Scout Bureau
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Fri Mar 02, 2007 10:29 am Post subject:
I assume that there's no tool like gdb/CHUD/Sampler on the computer in question? top is definitely indicating it's somewhere within our stuff, so now the trick's going to be to try and isolate exactly where within it It's definitely different then the high CPU load stuff I've been able to reproduce which is where other applications are hogging CPU. I've not seen this one yet myself, unfortunately.
This combination of 2.1 EA and patches causes a new (mis)behaviour.
I open an existing document. I print it (no editing at all). I close it by clicking on the red traffic light.
The document seems to have closed but I am left with an 'empty' white window.
It would have been nice to have a sample of the process.
Seriously, you aren't giving me any data to go on here. I've run out of guesses so until there is some real data to work with (Ed is the only one to provide me with any meaningful data so far), don't expect any new fixes.
It would have been nice to have a sample of the process.
Seriously, you aren't giving me any data to go on here. I've run out of guesses so until there is some real data to work with (Ed is the only one to provide me with any meaningful data so far), don't expect any new fixes.
In view of the increasing interest in these incidents, and its impact on 2.1 EA now confirmed, I will (on Monday) carry out my original idea to try to set-up one of our other similarly configured iMac G5s and see if we can trigger this effect on it. I'll seek agreement that we can take one out of production to dedicate some time on it to this task. I can certainly justify this in terms of present and future productivity.
Assuming that I'm going to see this effect, Ed, can you PM with the basic instructions to get the kind of data Patrick needs out of the dev tools that I'll also install on it. _________________ Ray Saunders
World Scout Bureau
You know, I wonder how long these instructions have been posted in NeoWiki and yet no one will cough up a damn sample.
I understand that NeoOffice is using a lot of CPU. I also know that Java is seriously fubar since the Java update. Jumping up and down and screaming that it uses too much CPU is not going to fix your problem. Providing samples of NeoOffice running so that I can see where Java is spinning its wheel is.
I want everyone to clearly understand what I am saying here: I am trying to fix Apple's Java code. Java is seriously broken here. Either I will be able to hack into Java or I won't. You can either continue complaining about symptoms or you can provide me data using the well-documented steps that, quite frankly, you should already know about.
I also want you to clearly understand what is at stake here: if Java is now too unstable to rely on and I cannot fix Java myself, one clear option is to pull NeoOffice downloads and leave it as a "build-it-yourself" project. I don't like that option, but I also am not going to spend every day hearing a flood of people complain about something that I cannot fix here and in Bugzilla.
I am not complaining - I was seriously trying to help you. I just know that it was weird all of a sudden and i did the command in terminal just as you asked me too.
sorry - Maybe I will go back to Pages and appleworks.
I am not complaining - I was seriously trying to help you. I just know that it was weird all of a sudden and i did the command in terminal just as you asked me too.
"Complaining" was a poor choice of words on my part. Substitute "describing the pain instead of the specific symptoms" is closer to what I am trying to get at. It was several posts ago that rays confirmed that CPU is high. Several more "me too's" didn't add any new data and merely serve to focus more pressure on me to fix Apple's screw up without giving anything to help solve the problem.
The key to any bug is reproducibility. For those who are not aware, there is a detail guide for how to file bugs. Although we are talking about a bug in a forum instead of Bugzilla, the same issues apply.
I would like to fix this bug. I may seem blunt and harsh sometimes, but my experience is that sometimes that is needed to get people to refocus in the right direction. I know that rays knows about sampling an application as he has done it in the past for many bugs. The fact that he wasn't doing it indicated to me that people were fixation on a single diagnostic tool and ignoring the others that we use.
The document seems to have closed but I am left with an 'empty' white window.
Did you reboot the computer after installing the test patch? If not, Java has probably already maxed out the Mac OS X Window Server with dead, unreleased windows so running NeoOffice a second time even with the test patch will just pile on more load to the already overwhelmed Window Server process.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
It's definitely different then the high CPU load stuff I've been able to reproduce which is where other applications are hogging CPU. I've not seen this one yet myself, unfortunately.
