[framework-issues] [Issue 94345] OOo runs amok when it cann ot accept on the pipe specified with the acce pt=pipe... command line argument
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94345 User sb changed the following: What|Old value |New value CC|'mba' |'mba,sb' --- Additional comments from [EMAIL PROTECTED] Fri Sep 26 07:28:51 + 2008 --- Related to this, the fix for issue 63110 prevents crashes that appeared in this scenario at least on Linux. It does not fix any of the issues mentioned here, however (CPU consumption, memory leak, non-termination). - 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]
[framework-issues] [Issue 94345] OOo runs amok when it cann ot accept on the pipe specified with the acce pt=pipe... command line argument
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94345 User kso changed the following: What|Old value |New value Assigned to|kso |cd --- Additional comments from [EMAIL PROTECTED] Fri Sep 26 08:03:15 + 2008 --- cd: Please take over. - 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]
[framework-issues] [Issue 94345] OOo runs amok when it cann ot accept on the pipe specified with the acce pt=pipe... command line argument
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94345 User cd changed the following: What|Old value |New value Status|NEW |STARTED --- Additional comments from [EMAIL PROTECTED] Fri Sep 26 08:18:31 + 2008 --- cd: Accepted. - 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]
[framework-issues] [Issue 94345] OOo runs amok when it cann ot accept on the pipe specified with the acce pt=pipe... command line argument
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94345 Issue #|94345 Summary|OOo runs amok when it cannot accept on the pipe specif |ied with the accept=pipe... command line argument Component|framework Version|OOO300m7 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|kso Reported by|fs --- Additional comments from [EMAIL PROTECTED] Thu Sep 25 19:38:42 + 2008 --- - start OOo 2.4.1 as follows soffice.exe -accept=pipe,name=fs93730;urp - wait until OOo 2.4.1 fully started - start OOo 3.0 RC 2 (OOO300.m7), with the same -accept=...-argument - after OOo 3.0 RC 2 fully started, watch the respective soffice.exe process in the task manager (or any other appropriate tool, like the Process Explorer) = the memory consumption of is constantly growing, though you don't do anything in OOo. I saw numbers up to 1.x GB (!) before this stopped, probably just because the OS didn't fulfill OOo's memory requests anymore - close OOo 3.0 RC 2 (File/Exit) = the respective soffice.exe process does not vanish from the task manager, instead, it keeps running, still and again with a constantly increasing memory consumption - 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]
[framework-issues] [Issue 94345] OOo runs amok when it cann ot accept on the pipe specified with the acce pt=pipe... command line argument
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94345 User fs changed the following: What|Old value |New value Target milestone|--- |OOo 3.x - 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]
[framework-issues] [Issue 94345] OOo runs amok when it cann ot accept on the pipe specified with the acce pt=pipe... command line argument
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94345 User fs changed the following: What|Old value |New value CC|''|'mba' --- Additional comments from [EMAIL PROTECTED] Thu Sep 25 19:50:49 + 2008 --- fs-kso: I am actually not sure you're really the right owner of this issue ... There are two problems here. One is in Acceptor::run in desktop/source/offacc: This is set up to accept an arbitrary number of incoming connections, by calling XAcceptor::accept on an Acceptor instance created from the value of the -accept= command line argument. Unfortunately, this call to XAcceptor::accept raises a ConnectionSetupException - not because it is unable to connect to a client which tried to establish a connection, but because it could not even open the pipe which it would use to listen for incoming connection requests. Sadly, Acceptor::run ignores those exceptions, and continuously calls XAcceptor::accept. This would be right if the exception were because a particular incoming connection could not be accepted, but in this situation, it is actually wrong. That is, since the named pipe is already blocked by another process, subsequent attempts to use it will all fail - this way a complete CPU is busy with just cycling through the loop, continuously failing to create the pipe. The second problem, and this is why I initially assigned this to you who you seem to have stakes in the io module, is that there's a memory leak in the pipe acceptor implementation. That is, with every exception raised in PipeAcceptor::init (io/source/acceptor/acc_pipe.cxx), a small amount of memory is lost, which is the cause for the steadily increasing memory consumption of the process. So, I think two bugs need to be fixed: - Acceptor::run needs to distinguish exceptions related to a particular incoming connection from exceptions caused by the unavailability of the resource which establishes the acceptor. Otherwise, the thread will run continuously, blocking a complete CPU/core - the PipteAcceptor implementation needs to fix its memory leak - 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]
[framework-issues] [Issue 94345] OOo runs amok when it cann ot accept on the pipe specified with the acce pt=pipe... command line argument
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94345 --- Additional comments from [EMAIL PROTECTED] Thu Sep 25 19:54:15 + 2008 --- Oh, there's in fact a third bug: The loop in Acceptor::run does not terminate in the scenario described above, this way preventing the complete process to terminate. This is caused by the fact that the only termination condition is when XAcceptor::accept returns a NULL connection. However, since it simply raises an exception, this condition is not evaluated, so the thread runs forever (or until you manually kill the process). - 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]
