Bug 132257 - Hang pasting HTML from crashreport.libreoffice.org (chrome/vivaldi/opera)
Summary: Hang pasting HTML from crashreport.libreoffice.org (chrome/vivaldi/opera)
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-19 15:36 UTC by Telesto
Modified: 2022-02-04 03:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Inside Clipboard file (401.94 KB, application/octet-stream)
2020-12-06 13:55 UTC, Telesto
Details
zip of chrome and firefox clipboards and Writer documents created from them (136.98 KB, application/x-zip-compressed)
2021-02-18 11:35 UTC, James
Details
screenshot showing significantly different rendings in Firefox and Chrome (132.84 KB, image/png)
2021-02-18 11:36 UTC, James
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-04-19 15:36:14 UTC
Description:
Hang pasting HTML

Steps to Reproduce:
1. open https://crashreport.libreoffice.org/stats/signature/CompareSwOutlineNodes::operator()(SwNode * const &,SwNode * const &)
2. CTRL+A
3. CTRL+C
4. Open Writer & CTRL+V -> Hang

Actual Results:
Hang

Expected Results:
No hang


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.alpha0+ (x64)
Build ID: 4475bcd83aac7e033fc5250f268eb922bd471e7b
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 1 Xisco Faulí 2020-05-13 11:10:52 UTC
Not reproduced in

Version: 7.0.0.0.alpha1+
Build ID: 1ffe59ef31186e36ad0aa7bbcdd32e407ee8d26c
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

using Firefox or Chrome.

Does it hang forever and eventually you have to kill LibreOffice or is it just a few seconds ?
Comment 2 QA Administrators 2020-11-11 04:18:39 UTC Comment hidden (obsolete)
Comment 3 Telesto 2020-12-06 13:55:44 UTC
Created attachment 167866 [details]
Inside Clipboard file
Comment 4 Telesto 2020-12-06 13:56:46 UTC
Comment on attachment 167866 [details]
Inside Clipboard file

Wrong bugdoc
Comment 5 QA Administrators 2020-12-07 04:13:59 UTC Comment hidden (obsolete)
Comment 6 James 2021-02-18 11:30:49 UTC
_observed_
I cannot reproduce the hang described in comment 0 using the data in the referenced page today, but I can see different appearance, time to render, and editing in Writer when pasting content from Chrome vs Firefox.

If I use Ctrl-Shift-V to paste, I find that I only see this effect when choosing the "HTML Format without comments" option

If I inspect the clipboard content with Inside Clipboard, there is ~10x more HTML data from Chrome than Firefox.

I attempted repro with Writer versions 6.1.2.1, 7.0.0.0.alpha1, and 7.1.2.0.0+. The edit lag particular is very noticeable when pasting from Chrome. 

_reproduce_

* Open Writer

Repeat for Firefox and Chrome:
* Browse to https://crashreport.libreoffice.org/stats/signature/CompareSwOutlineNodes::operator()(SwNode%20*%20const%20&,SwNode%20*%20const%20&)
* Click in the page
* Ctrl-A 
* Ctrl-C
* In Writer, File> New> Text Document
* Ctrl-Shift-V
* Choose "HTML Format without comments"
* wait for the content to render
 => takes longer in Chrome than Firefox
 => there are noticeable differences in rendering

* click in a rendered table cell and enter some text
 => there is significant delay in the edits appearing in data pasted from Chrome

* scroll the document
 => there is significant delay in the edits appearing in data pasted from Chrome


_exhibits_
I'll attach a zip of the content saved from Chrome and Firefox in each of Writer 6 and 7, and the Inside Clipboard content for Chrome and Firefox.

_related issues_
I looked for similiar issues and found bug 138226 but I don't see the edit lag there when pasting content from Chrome or Firefox.

_notes_
If you prefer this observation as a separate ticket, please say and I'll create one.

_versions_
Version: 6.1.2.1 (x64)
Build ID: 65905a128db06ba48db947242809d14d3f9a93fe
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
Locale: en-GB (en_GB); Calc: CL

Version: 7.1.2.0.0+ (x64) / LibreOffice Community
Build ID: 90294a92f15218bfd18986053dfeeaeaa99c2fd8
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded

Version: 7.0.0.0.alpha1 (x64)
Build ID: 6a03b2a54143a9bc0c6d4c7f1...
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win; 
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded
Comment 7 James 2021-02-18 11:35:37 UTC
Created attachment 169850 [details]
zip of chrome and firefox clipboards and Writer documents created from them
Comment 8 James 2021-02-18 11:36:42 UTC
Created attachment 169851 [details]
screenshot showing significantly different rendings in Firefox and Chrome
Comment 9 Xisco Faulí 2021-07-07 11:08:33 UTC
Hi Telesto,
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Comment 10 QA Administrators 2022-01-04 03:29:56 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2022-02-04 03:42:14 UTC
Dear Telesto,

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-FollowUp