Apache OpenOffice (AOO) Bugzilla – Issue 81186
Sun Report Builder extension causes OOG680_m3 to crash
Last modified: 2007-09-05 23:32:32 UTC
Using a self compiled OOG680_m3 X11 version on my Intel Mac Mini I can install the Sun Report Builder extension from http://extensions.services.openoffice.org/project/reportdesign When I try to use it by clicking on "Create Report in Design View" OOo seems to load something but crashes after 15 seconds. This is a MacMini with CoreDuo, 1,25GB of RAM, Mac OS X 10.4.10 with all the latest secupdates etc pp.
Confirmed
.
set as release_blocker for Mac X11
as discussed with macjogi and mechtilde on IRC setting priority to P1.
cannot reproduce. PL kindly built a OOG680_m3, X11 version, from scratch. Installed the extension, opened the Bibliography database, opened the report design. No problem at all.
hmm .. not so fast They are several people, used to debug and track issues, who have problems, and who confirmed the issue. Can we have more infos about pl build ? New mozilla packages , e.g .. something who could help us Thanks in advance
Okay, didn't know this was a problem affecting more people than the original submitter. No offense intended, but there was this "self compiled" :) Re-opening then. fs->pl: Eric asked for details of your build, which I cannot provide, since I don't know anything about it. fs->*: If anybody of you is able to get a stack of the crash, this would be highly appreciated. fs->self builders: Does it make a difference if you install the extension from <source>/reportdesign/unxmac*/bin, as opposed to the version at extensions.services.openoffice.org.
It seems to be a different if you install the extension with unopkg in a terminal. Or you install with the OOo GUI
Created attachment 47949 [details] text file of the gdb output
Created and attachment that shows the output of gdb. when starting OOo in gdb mode OOo does not crash but freezes. When starting OOo the normal way OOo exits. I used clean OOG680_m3 sources for the build but I can do a second checkout and build again to verify the issue. I will also try and install the extension out of the mentioned unxmac* directory. maveric->fl: Did you use "Create Report in Design View"? Using the wizard doesn't cause OOo to crash.
You use a non-product build (configure switch "--enable-dbgutil"), correct? If so, does it make a difference if you use a product build (which is what PL and /me did)? Other than this, the stack is rather useless to me :( Looking into what can have caused the assertion in documentdefinition.cxx:700, something is strange. It means that either xFrame is NULL (line 692), which would imply a document has been loaded (since xController is not NULL), but not put into a frame. Quite impossible, I'd say. Or, it means that xFrame is not NULL, but does not support XComponent - impossible, too. Somehow this tastes like some kind of corruption to me. Since Mechtilde mentioned unopkg: maveric, did you register the extension via GUI or with unopkg? Also, as shared or as user extension?
maveric tested the GUI ericb tested also with unopkg as maveric said this morning in IRC
maveric->fs: pjanik told me to recompile the libraries using "--enable-dbgutil" so I did this. An OOG680_m3 with sources as of today morning and without "--enable-dbgutil" is currently building on this Mac but will take a while to finish it's just in the fourth module or so. As mechtilde wrote: I used the GUI to install the extension. I installed it as a user extension.
> maveric->fs: pjanik told me to recompile the libraries using > "--enable-dbgutil" so I did this. which is great, non-product versions have a high number of additional diagnostics, which greatly ease debugging, usually ...
maveric->fs: Using clean sources as of today and a freshly compiled OOo it doesn't crash when using the Sun Report Builder extension or any other extension. Looks like it was me checking out m3 sources too early. I'll let others do some testing with this build and if they confirm that it works for them too, we can close this issue. When I try to install the sun report builder extension that is build with OOo I get an error: Cannot find a localized license text or a default license text. But this is maybe another issue.
Okay, this sounds good so far. The license text issue is issue 81019, which according to EIS should be fixed in m3. Hmm. Pavel, as the original submitter, can you confirm this still happens in m3?
yup, license is ok, I have just closed #i81019#.
pjanik just noticed that I at least one module out of m2 sources. I need to verify it with clean m3 sources. For so long please don't close this issue.
pjanik just noticed that there was at least one module out of m2 sources. I need to verify it with clean m3 sources. For so long please don't close this issue.
A second build with real clean sources in a complete different directory no longer shows the mentioned behaviour. Sun Report Builder can be installed and the build extension has the license text. Did a second test with official Mac OS X11 binaries from maho to verify that the extension works. If rbircher confirms this issue can be closed.
Confirmed, pleas close issue, thanks I will test it with Mahos build if rc2 is aviable. But I think it's ok Raphael
closing