To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=55193
User rainerbielefeld changed the following:
What |Old value |New value
================================================================================
CC|'' |'rainerbielefeld'
--------------------------------------------------------------------------------
Component|Word processor |framework
--------------------------------------------------------------------------------
Priority|P1 |P3
--------------------------------------------------------------------------------
QA contact|[EMAIL PROTECTED] |[EMAIL PROTECTED]
--------------------------------------------------------------------------------
Subcomponent|viewing |ui
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Sep 28 08:59:50 -0700
2005 -------
The actual OOo design seems to normal that no other OOo can be used in a normal
way if another one causes 100% CPU load.
I can not decide
* what is OS's task to distribute ressources "fairly" and expedient
* what is OOo's responcibilyty not to overload system?
I can confirm with 2.0 (1.9.m125) German version WIN XP: [680m125(Build8947)],
that OOo is more or less blocked, if one of the running OOo tasks is
"overloaded, while I can work with other running WIN-applications with only
little restrictions (Athlon 3200+, 1GB).
Seems to be a FEATURE request.
---------------------------------------------------------------------
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]
