Eric Hoch wrote:
Hi all,
Am Fri, 29 Feb 2008 06:54:29 -0800 schrieb Rodney D. Myers:
OS X 10.5.2 (3 3 day old new MBP), OO 2.4
(OOo_2.4.ORC1_MacOSXIntel_X11_install,dmg)
OS X 10.5.2 - all the latest security patches installed.
OOo_2.4.0RC2_MacOSXIntel_X11_install_de.dmg - selbst kompiliert, da
ja noch kein offizieller Build von Maho da ist.
Of all of the programs I needed to re-install (all of them), OO
is the only one not to open.
After compiling RC2 of OOH680_m8 under Mac OS X 10.4.10 I can
confirm this for upcomming 2.4.0.
Under Tiger: Everything is just fine and OOo starts in about a
second, takes some time to convert the fonts, comes up. Fine.
Second start, OOo is up just as fast as 2.3.1 was.
Leopard: Double Click on the Startup Script. OOo takes ages until
it asks if I want to convert the system fonts. The answer has no
affect on the outcome it's always a never starting OOo.
I do know, if I open a shell/terminal and run the same command;
sh /Applications/OpenOffice.org 2.4.app/Contents/MacOS/soffice
OO starts. If I try, and click on the icon, nothing happens. Even
though is shows when running "ps aux"
Any ideas as to what might be happening?
When I run from the shell, I get this as an output within the shell;
bin/OpenOffice.org
2008-02-28 14:59:26.077 soffice.bin[4591:2d03] ***
_NSAutoreleaseNoPool(): Object 0x225be30 of class NSCFArray
autoreleased with no pool in place - just leaking
Stack: (0x94f8012f 0x94e8cec2 0x94eb3c64 0x4574976 0x3bc6611
0x3bc777c 0x3bc9247 0x3b8d62c 0x3b8db31 0x3b95182 0x3c46634
0x3c4505a 0x3c4b2bc 0x3c484ec 0xd10bf6 0x455d6d3 0x45609ee
0x455c7fe 0xe2f370 0xe2ea96 0xe2ed5b 0xe31d30 0xe2ea96 0xe2edb9
0x25ad487 0x25a2245 0x4242cc 0x4252ee 0x3f9077 0x244484f
0x2407ee9 0x2409eda 0x2443331 0x57c7e8 0x5088f8 0x508a63 0x58ce8f
0x5244fd 0x2773e07 0x277411a 0xe2f370 0xe2ea96 0xe2edb9 0xe2f937
0xe2ff19 0xe31a86 0x25ad908 0x25a22a6 0x1519d 0x15ab6 0x3d2241
0x3d2318 0xf0e24c 0x94255c55 0x94255b12)
I see exactly the same error messages here in my terminal and my
log file. It doesn't seem to have any impact on the usability of
OOo, meaning that OOo is usable and so far it doesn't seem to be a
memory leak that consumes huge amounts of memory in about a second
but I'm with 2GB of RAM - the max for my Mac Mini so maybe I'm not
the one to make a comment on this.
I've seen the same error when running VCL testtool on Tiger. Maybe we
do have a leak in the OpenOffice.org code and Leopard is just more
sensitive to it. Maybe it is time to run a code cleaner on
OpenOffice.org source code and find the memory allocation code without
an associated memory free code.
James McKenzie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
