Apache OpenOffice (AOO) Bugzilla – Issue 97425
Crash, when ending a basicprogram under special circumstances
Last modified: 2017-05-20 11:28:08 UTC
Starting a basic-program (self-build-extension), program opens a dialog, open an new writer document with that program without closing the dialog. Now the dialog is "glued" at the second (new) window. Closing the first window (from that the program was original started), working with the program - no problems. Finishing the program -> Crash! The ID of the first error report is r86rwuc. More IDs will follow
can confirm also with OOO300_m13 and DEV300_m37
well that can have different reason. Without knowing the basic macro and what are you doing exactly it is impossible to say where the problem is. You can easy damage the office with own macros by doing the wrong things ...
The ID of the first error report is r86rwuc. Also we get:rkcrwuc rjnrwuc rd5rwuc rj7rwuc rkxrwuc
again please give us the basic code that we can take a look on it. It doesn't make sense to produce more crash reports.
I attach an example extension This code is the part causing the crash. The UI is in German.
Created attachment 59245 [details] Extension showing the crash
jsc -> ab: the basic code looks ok for me. I think we need some deeper debugging
STARTED
ab->mikeadvo: I could not reproduce this, neither on OOO300m9 nor on dev300 m45. First, I don't find the dialog glued to the new opened window but to the first one. Second, I can't close the first window at all. Did I understand anything wrong?
mikeadvo -> ab I tested it with OOO300m9; bug still there. Itry to give you a step-by-step-introduction: you have to click "Dokument freigeben" ("Free document") an then on "Auswahl" ("choice"). A messagebox with a warning will appear: "Dieses Fenster darf nicht vor der Beendigung dess Programms geschlossen werden, da OpenOffice.org sonst bei Beendigung des Programms abstürzt!". Click on "ok". A new window will appear and the dialog will glue a this new window, so you can close the first one. Do this and then click on "Programm beenden" ("finish program") and "Auswahl". -> Crash If you opened a third window from the first one, dataloss is possible.
ab->mikeadvo: I could reproduce this now. I think the problem is that by this complex scenario you've managed to allow the window used to start the program is beeing closed which normally, e.g. in case of a document containing a macro, is blocked just to avoid problems like this. I doubt that this is easy to fix. As this is a very complex scenario that should not "affect a sig- nificant number of customers", I don't think, P2 is justified, see: http://qa.openoffice.org/scdocs/ddIssues_EnterModify.html#priority So STARTED, P3, OOo 3.x for now.
mikeadvo -> ab P3 is also ok for me. But I don't think, this problem doesn't "affect a sig- nificant number of customers". OOo is more and more going to business (that's good, I suppose ;-)). In such an enviroment extensions and Makros are needed. So it's a common problem to "free" the window used to start the program and it's easy to realize that in Basic.
> But I don't think, this problem doesn't "affect a sig- > nificant number of customers". OOo is more and more going to business (that's > good, I suppose ;-)). In such an enviroment extensions and Makros are needed. I did not mean the number of OOo and macro users in general, but the number of users running into this special problem. > So it's a common problem to "free" the window > used to start the program and it's easy to realize that in Basic. Really, this is a common problem? I have to admit, I've never heart of it before. Why to you want to "free" a window and from what? From the modal dialog? I doubt that "a significant number etc." uses macros that have to run all the time kee- ping a dialog open all the time. What's the reason for this by the way? There must be alternatives. :-)
Reset assigne to the default "issues@openoffice.apache.org".