https://bugs.freedesktop.org/show_bug.cgi?id=70703
--- Comment #25 from [email protected] --- I'm still hoping that someone will look at this at some point. I have spent countless hours trying to circumvent it and to replicate in a simpler form. I have done some experiments which may shed some light on possible causes. I have a form (A) with a subform (S). In subform (S) I go to a 'new record', and then use a button to select another form (B) which will determine part of the essential content of subform (S). This invokes a dialogue, which I use to open the form (B). All is fine so far. On form (B) I 'select' the item I want. This invokes a macro to store the key to the selected record in subform (S) and then close form (B). At the point at which this value is stored in subform (S) the 'beforeupdate' event is triggered in subform (S) (and it seems this usually happens before the calling macro ends). The calling form (A) and subform (S) may be made visible before or after this value is stored (I have tried both with no change to the result). This beforeupdate event does a number of calculations and database lookups to complete the data required for the record in subform (S). It is invoked twice - once for the database form and once for the document (as is true for all beforeupdate events - strange are the ways of LibreOffice Base events). The second call does almost nothing. There is also an AfterUpdate event macro which does almost nothing (it used to but I suppressed it in order to find the cause of the crash). If I let all this run it crashes every time. If I place a breakpoint in the beforeupdate event (with the Basic IDE) at a point that is invoked only once, and wait briefly before resuming execution, it does not crash. I tried inserting a 'wait 2000' instead of a breakpoint, but that did not work. Other examples of the crash are less repeatable, which made me think it is related to some sort of timing issue between screen handling and macros running in the background. I have found that when there is a lot of macro processing going on at the time a form is being updated and receiving the focus on screen, crashes are more likely. I have simplified my explanation of the number of macro actions occurring somewhat, but the above gives the essence. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
