Reproduction instructions: 1. Create a new spreadsheet 2. In a browser, show the dependency tree, with resolved, of a large LibreOffice metabug on Bugzilla - say, > 750 bugs, some sub-bugs etc. 3. Collapse some of the sub-bugs (not sure this part matters...) 4. Select all dependent bug items on the HTML pages, i.e. from the first to the last, full lines 5. Paste into Calc 6. Press Ok (don't enable any special settings) 7. Wait a few moments Expected result: You see some kind of import result of the tree of bug numbers and titles. Actual result: You wait and and wait and nothing happens (or the OS tells you the app no longer responds)
(In reply to Eyal Rozenberg from comment #0) > 2. In a browser, show the dependency tree, with resolved, of a large https://wiki.documentfoundation.org/QA/BugReport#Minimum_requirements > Actual result: > You wait and and wait and nothing happens (or the OS tells you the app no > longer responds) takes ~10s for the 42 items of https://bugs.documentfoundation.org/showdependencytree.cgi?id=80430&hide_resolved=1 Version: 24.2.4.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 12; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 4:24.2.4-0ubuntu0.24.04.2 Calc: threaded
(In reply to fpy from comment #1) > https://wiki.documentfoundation.org/QA/BugReport#Minimum_requirements Fair enough. URL of page I was copying from: https://bugs.documentfoundation.org/showdependencytree.cgi?id=119352&hide_resolved=0 LO build: Version: 24.2.4.2 (X86_64) / LibreOffice Community Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2 CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US but if I save the URL to local disk, HTML-Only, load it in a browser, and perform the same copy-pasting, the import concludes in a couple of seconds. inxi machine info: CPU: quad core Intel Core i5-7600K (-MCP-) speed/min/max: 3562/800/4200 MHz Kernel: 6.6.13-amd64 x86_64 Up: 14d 23h 36m Mem: 9.31/15.5 GiB (60.0%) Storage: 5.91 TiB (41.3% used) Procs: 327 Shell: Bash inxi: 3.3.35 > takes ~10s for the 42 items of > https://bugs.documentfoundation.org/showdependencytree. > cgi?id=80430&hide_resolved=1 Ok, even that is a huge amount of time.
My guess is that the delay is generated by (having to repeatedly paste) the icon of each bug item.
(In reply to Eyal Rozenberg from comment #2) > ... save the URL to local disk good move. so, with a bit of more experiments, we can see : - it's actually the (repetitive) fetching of icons from bugs.documentfoundation.org which creates the lag. - it's not a matter of copy/paste, neither of calc : if you open the file directly with writer, the symptoms are the same. when on filesystem, or a localhost http test server, response times are within seconds. see attached archive. would clearly be resolved as NOTABUG, NOTOURBUG ... or maybe a very niche enhacement request.
Created attachment 195799 [details] simplistic examples with 100 line HTML.
(In reply to fpy from comment #4) > - it's actually the (repetitive) fetching of icons from > bugs.documentfoundation.org which creates the lag. Not really, for two reasons: 1. There shouldn't be any repetitive fetching, just one fetch. Repetitive fetching of the same URL is a bug in itself. Do we repeat fetches? 2. Even if we were to repeat fetches - that's not a reason to have unresponsive UI for a long amount of time, and have the OS want to kill you. > when on filesystem, or a localhost http test server, response times are > within seconds. > > would clearly be resolved as NOTABUG, NOTOURBUG ... Uh, no, not at all. It is a bug (or multiple bugs) and definitely our bug. > or maybe a very niche enhacement request. Copying and pasting from a web page into a document is not niche.
(In reply to Eyal Rozenberg from comment #6) > > would clearly be resolved as NOTABUG, NOTOURBUG ... > > Uh, no, not at all. It is a bug (or multiple bugs) sorry, I should have explicitely added DUPLICATE https://bugs.documentfoundation.org/show_bug.cgi?id=45307#c23
(In reply to fpy from comment #7) > sorry, I should have explicitely added DUPLICATE Ah, well, that's something else. Fair enough. *** This bug has been marked as a duplicate of bug 45307 ***