Bug 137718

Summary: Crash when exporting/registering odt file in html format when html file already exist
Product: LibreOffice Reporter: Daniel <tech>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: ilmari.lauhakangas
Priority: medium    
Version: 7.0.1.2 release   
Hardware: x86-64 (AMD64)   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Daniel 2020-10-24 12:04:55 UTC 
Description:
Hi,
on a customer MacBook Pro (2020) with 7.0.x LibreOffice version (at this time 7.0.2) when trying to export or register an odt file in html format LibreOffice crash without writing the file and become very slow. Closing the application and starting it again make it work normally. Deleting the html file before exporting/registering has not this behaviour and work well.

Steps to Reproduce:
1.create odt file
2.export html format
3.

Actual Results:
crash

Expected Results:
should write the file even if already existing


Reproducible: Always


User Profile Reset: No



Additional Info:
Exporting odt in html file should be possible without crash when the file is already existing.
Comment 1 mrei 2020-11-02 04:42:01 UTC 
Working for me. I am exporting in html format, no problem. When I am rewriting over the same file no speed issue, no crash.

Version: 7.1.0.0.alpha1
Build ID: 987671387712c4f9061d6216ff2f001a7bb9e57b
CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 2 Daniel 2020-11-07 16:38:39 UTC 
So will wait that 7.1 comes out
Comment 3 Buovjaga 2020-11-10 09:23:30 UTC 
(In reply to Daniel from comment #2)
> So will wait that 7.1 comes out

I think it is a good idea to test immediately with a daily build: https://dev-builds.libreoffice.org/daily/master/current.html

It is possible that this was closed too soon
Comment 4 Daniel 2020-11-10 09:49:39 UTC 
Hi,
I can't/won't install a daily version at a customer location,sorry. Close the bug if you need, I will reopen it/or create a new one if problem still persist.
Comment 5 Daniel 2020-12-05 13:44:18 UTC 
The bug disappears with 7.0.3 version