https://bugs.documentfoundation.org/show_bug.cgi?id=92617

--- Comment #5 from t...@tim-passingham.co.uk ---
Created attachment 117180
  --> https://bugs.documentfoundation.org/attachment.cgi?id=117180&action=edit
Test case database

This was not easy to reproduce, but I have just managed to do so in the
attached self-contained database. 

I don't know if all the complexities and features included in the demo are
require to generate the crash.  

There are 4 tables.  Table1, with Table2 containing records that depend on
Table1 records and also depend on Table3 records.  Table4 has records that
depend on Table3 records.  

There are 2 forms.  Table1 has Table1 records with a subform for Table2 records
linked to Table1.  

Table3 has Table3 records with a subform for Table4 records linked to Table3.

To make it crash follow these steps:

1. Open Table1 form
2. Enter text in text1
3. Enter text in text2 (which is in the Table2 subform)
4. Press button 'Open Table3'
5. Enter text in text 3
6. Enter text in text 4 (which is in the Table 4 subform)
7. Press the Exit button (do nothing else - if you put the cursor in a Table3
field first it may not crash)
8. LO Base will ask you 'Do you want to save your changes'
9. Press Yes
10. It should crash.

There are 4 (very ugly) macros created for testing this.  Table4BeforeUpdate is
the 'before update' routine for the Table4 subform.  OpenForm is the routine
for opening the Table3 form from Table2.  ExitTable3 is called when the Exit
button is pressed on Table3.  CloseTable3 is called as the 'Document is going
to be closed' routine on Table 3.

The crash seems to be due to some sort of timing problem.  When debugging in
Table4BeforeUpdate there is a nested call to the 'before update' routine for
the Table 4 subform.  I had to add a delay to that routine to make it crash. 
In my real system I just do a lot more work in the equivalent forms that
creates a long enough delay for the crash to occur more often than not.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to