To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=47944
------- Additional comments from [EMAIL PROTECTED] Mon May 2 02:58:43 -0700 2005 ------- The gettimeofday calls are used for OOo's internal timers to check whether a timer has run out and should be handled. They occur basically as often as either an X event occurs or a timer runs out; so that's quite normal. I fear gettimeofday has just proven again that looking at a strace output tells you next to nothing about OOo. The only way this would indicate something interesting would be if someone in OOo sets up a high frequency timer (say a few millicseconds) and then does something time consuming inside the handler. What would seem more promising would be breaking into OOo occasionally with gdb to see what actually is taking so much CPU. I'd do so myself, but an idle writer document takes 0.0% on my machine. Just my 2 cents --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
