Summary: | Calc: Feature request following closure of bug 43008 (Pasting into column causes hang) | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Richard Parkins <aleph0hpela-bugz> |
Component: | Spreadsheet | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | medium | CC: | barta, mcavalleri91, qubit, raal |
Version: | 4.2.6.3 release | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.freedesktop.org/show_bug.cgi?id=43008 https://bugs.freedesktop.org/show_bug.cgi?id=68156 |
||
Whiteboard: | perf possibleRegression | ||
i915 platform: | i915 features: |
Description
Richard Parkins
2014-11-02 16:54:07 UTC
Hello, tested with string/numerical values - paste into whole column is in few seconds - no bug here. Copy rows with formula A1=1 A2=2 A3=A1+A2 program freeze, high CPU etc. Tried with excel - copy string/numerical values is the same behaviour as in Calc. - Copy rows with formula A1=1 A2=2 A3=A1+A2 excel copy only this three cells. Hi. Something else is needed. A logger plug-in that monitor performance in that kind of situation in order to write better bug reports and confirm the defect. (In reply to rinvel from comment #2) > Something else is needed. > A logger plug-in that monitor performance in that kind of situation in order > to write better bug reports and confirm the defect. Hi Rinvel, We do have tools for debugging LibreOffice: https://wiki.documentfoundation.org/Development/How_to_debug Whiteboard -> perf (In reply to Richard Parkins from comment #0) > I don't know how MS Excel does a paste of a single number into a column so > quickly...Presumably it would require significant surgery to make LO do this. I'm not sure, but yes, it could take a lot of time to fully-implement this feature. > a fallback solution would be to put up a > dialog box with some sort of estimate of how long it will take, and ask the > user if they really want to do it. Creating the dialog box would be easy; deciding when an operation will take a long time will be harder. No guarantees that this "fallback" solution will be an easy fix. At the end of the day, we'd really like to avoid LibreOffice hanging due to basic user operations such as cut and paste. So status -> NEW. We need is an easy-to-use extension for end user : the methods you provided are for developers not for end users. We also need to consolidate all the duplicate bugs that report the problem. Each one is a different way to reproduce the bug. (In reply to raal from comment #1) > Hello, > tested with string/numerical values - paste into whole column is in few > seconds - no bug here. Raal -- take a look at the repro steps in bug 68156 comment 9. (In reply to rinvel from comment #4) > We need is an easy-to-use extension for end user : the methods you provided > are for developers not for end users. I'd love to have powerful tools that are built for end users, but I don't know of any that would help in this case. Right now, the developer-centric tools are our best bet at tracking-down performance issues. > > We also need to consolidate all the duplicate bugs that report the problem. > Each one is a different way to reproduce the bug. Bug 43008 has a couple of dupes, but at first glance they all look similar. To keep things simple, I'd either stick with the repro steps we have, or make a short comment pointing at the repro steps in other report comments (as I did in this comment above) Does LO have a log / an error log / a dump file / a verbose mode we could use or activate ? In the case of a problem the file could then be audited. (In reply to rinvel from comment #6) > Does LO have a log / an error log / a dump file / a verbose mode we could > use or activate ? If you run LibreOffice in a terminal, you can see some error output useful for debugging. > > In the case of a problem the file could then be audited. Sure, but how would such a file help in this case? (In reply to Robinson Tryon (qubit) from comment #5) > Raal -- take a look at the repro steps in bug 68156 comment 9. FWIW, LO 3.3.0.4 is much snappier with the copy/paste in attachment 111136 [details] (testing on Ubuntu 14.04): (Approximate times) ------------------- 3.3.0.4: 8 sec 3.5.7.2: 15 sec 4.0.6.2: 15 sec 4.1.2.2: 60+ sec (Killed process) Perhaps LibreOffice could have a 'Cancel current operation' button? That way we wouldn't have to make a judgment call about whether an operation is taking a long time or the application has hung and will never finish. > FWIW, LO 3.3.0.4 is much snappier with the copy/paste in attachment 111136 [details]
> [details] (testing on Ubuntu 14.04):
>
> (Approximate times)
> -------------------
> 3.3.0.4: 8 sec
> 3.5.7.2: 15 sec
> 4.0.6.2: 15 sec
> 4.1.2.2: 60+ sec (Killed process)
Thus the bug should be considered a Regression and not a feature request, shouldn't it?
(In reply to Teo91 from comment #9) > > FWIW, LO 3.3.0.4 is much snappier with the copy/paste in attachment 111136 [details] > > [details] (testing on Ubuntu 14.04): > > > > (Approximate times) > > ------------------- > > 3.3.0.4: 8 sec > > 3.5.7.2: 15 sec > > 4.0.6.2: 15 sec > > 4.1.2.2: 60+ sec (Killed process) > > Thus the bug should be considered a Regression and not a feature request, > shouldn't it? My guess is that some operations are taking longer because of increased complexity in the mechanisms underneath Calc. The time to perform certain operations has indeed increased, however I'm not sure if the Calc devs would see this as a regression. I'm going to mark this as a possibleRegression and let the devs weigh-in. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.