Bug 106793 - App hang after opening a second (existing) document
Summary: App hang after opening a second (existing) document
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-27 11:28 UTC by f.heinemann
Modified: 2017-10-30 10:51 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description f.heinemann 2017-03-27 11:28:14 UTC
Description:
After working with one documend and open an existing second document the second writer instance hang (not responding). Closing this (second) application also close the first application by kill. Previous first open document is not closed (saved) properly. Next time stating writer writer try to recover first document.


Steps to Reproduce:
1.open an existing document and work with it.
2.open another existing document.
3.second instance of writer do not respond.


Actual Results:  
both instances are killed by closing the second (not responding) application. documents are not closed properly. recover dialog opens after restart writer app.

Expected Results:
working with two documents in parallel.


Reproducible: Always

User Profile Reset: No, because of losing all my settings.

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Xisco Faulí 2017-03-28 07:14:37 UTC
I can't reproduce it in

Versión: 5.3.1.1
Id. de compilación: 72fee18f394a980128dc111963f2eefb05998eeb
Subpr. de CPU: 1; SO: Windows 6.1; Repr. de IU: predet.; Motor de trazado: HarfBuzz; 
Configuración regional: es-ES (es_ES); Calc: group

Could you please try to open both documents in safe mode without resetting your profile?
Comment 2 f.heinemann 2017-03-28 07:59:17 UTC
But I have some more actual information concerning this issue. Occurence of issue depends on rank order of open the concerned documents. If I first open document1 and than document2 all works fine. If I open document2 and than document1 the issue occurs. Therefore I was looking for the properties of both documents and found one difference. Document1 don’t save fonts, but document2 save the fonts in document. In fact it seems to be a problem of loading the fonts with document. I also found that if both documents are open only one instance of soffice.bin and only one instance of swriter.exe are running. Maybe the problem is located in memory managment (font manager?). One additional information about document. Size of document (51 pages) without fonts is about 250kB, with fonts 10MB. If you at least open the document with saved fonts and wait about 30 seconds, the document opens, but this is not normal (MS Word open both documents, saved with fonts, on immediatly).
Comment 3 Xisco Faulí 2017-03-28 08:24:32 UTC
Please attach a sample documents, as this makes it easier for us to verify the bug. 
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 4 QA Administrators 2017-09-29 08:57:55 UTC Comment hidden (obsolete)
Comment 5 Xisco Faulí 2017-10-30 10:51:33 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20171030