From owner-freebsd-current Sat Apr 18 17:00:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01734 for freebsd-current-outgoing; Sat, 18 Apr 1998 17:00:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01724 for ; Sun, 19 Apr 1998 00:00:03 GMT (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id XAA01741 for ; Sat, 18 Apr 1998 23:59:59 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id TAA18624 for current@freebsd.org; Sat, 18 Apr 1998 19:59:57 -0400 (EDT) From: Mikhail Teterin Message-Id: <199804182359.TAA18624@rtfm.ziplink.net> Subject: Re: Star Office 4 (Was: Re: Problems w/ Linux EMU) In-Reply-To: <19980418111526.A7246@keltia.freenix.fr> from "Ollivier Robert" at "Apr 18, 98 11:15:26 am" To: current@FreeBSD.ORG Date: Sat, 18 Apr 1998 19:59:57 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" after staroffice 4 has been running for a few seconds it locks up and i do => a ipcs and see all my shared segments are used up. = =I have a script that start StarOffice4 and then clean up the shared memory =segments afterward (it is either a bug in SO4 or a bug in our shared mem =emulation). Same here. =I've been seeing SO4 lockups regularely too. Sometimes, you start doing =something then everything is blocked because it has gone in a tight loop, =taking huge amount of CPU. Only kill is effective. Did not happen to me yet. I'm not a heavy user though... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message