Bug 140453 - Standalone Forms crash leaving zombie processes
Summary: Standalone Forms crash leaving zombie processes
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-16 15:40 UTC by herman.viaene
Modified: 2021-07-08 09:53 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Database used by standalone forms (4.19 MB, application/vnd.oasis.opendocument.database)
2021-02-25 12:55 UTC, herman.viaene
Details
Standalone forms (1.19 MB, application/zip)
2021-02-25 13:01 UTC, herman.viaene
Details

Note You need to log in before you can comment on or make changes to this bug.
Description herman.viaene 2021-02-16 15:40:48 UTC
I have made a Base application consisting of an .odb with some 10 standalone forms. One being a start form that does nothing else but call the other forms by clicking on a button. It runs now on Windows 10 Home edition fully updated.
The user starts the application by the start form (which remains open all the time) and then opens and closes the proper application forms to her needs. After opening and closing such forms for maybe 20 times or more, LibreOffice crashes when closing a form. Up to now all data operations of the last form are recorded correctly in the odb file, that's good. But the crash leaves at least one zombie process running, which the user needs to stop in the Windows tasks, to be able to get on again.
I'v made the application on Linux Mageia, and there I've never came across this issue. But I have to admit that I never did do so many open/close operations in a short time.
Comment 1 Raji 2021-02-24 12:11:08 UTC
Hello Herman,

Thank you for reporting the bug.
Can you please provide a clearer set of step-by-step instructions on how to reproduce the problem. If possible please attach the documents too.

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided.
Comment 2 herman.viaene 2021-02-25 11:15:15 UTC
Making up a demonstration database and standalone forms. Hope to get ready tomorrow as original odb might be too big to attach.
Comment 3 herman.viaene 2021-02-25 12:53:13 UTC
With a small model the error seems not to occur. With the real application I have been able to provoke a crashreport.
It is at crashreport.libreoffice.org/stats/crash_details/208ba320-544f-413e-b6c6-e0824d088ada.
I'll try to upload the complete database.
Comment 4 herman.viaene 2021-02-25 12:55:27 UTC
Created attachment 170057 [details]
Database used by standalone forms

I will make a zip file of the standalone forms concerned.
Comment 5 herman.viaene 2021-02-25 13:01:31 UTC
Created attachment 170058 [details]
Standalone forms
Comment 6 herman.viaene 2021-02-25 13:11:04 UTC
The form to start with is called "Startscherm Volkstuintjes.odt".
It just presents buttons to open the other forms.
Procedure:
Make sure the forms refer to the registered database.
Open this form and click on the buttons to open one of the other forms.Keep the first "Startscherm Volkstuintjes.odt"always open. Don't mind what they show, just close the called form and open another one, close again,  etc... After some tries LO crashes.
This happens in Windows 10. the database has been developed in LO6.4 on a Linux Mageia machine and then copied to a Windows platform. The crashes have occured only on the Windows machines (tested on 2 machines) since the installation of LO7.0.4, not on the 6.4.
Comment 7 Xisco Faulí 2021-07-07 11:08:57 UTC
Hello,
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 8 herman.viaene 2021-07-08 09:53:24 UTC
On win10 removed first the existing 7.0.6 , rebooted and installed the 7.1.4.2 version. The problem does not seem to occur anymore, at least not as quickly as it did previously. I did not exercise it for hours.