Summary: | EDITING: HANG when copy - paste cells including merged ones to column | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Rainer Bielefeld Retired <LibreOffice> |
Component: | Spreadsheet | Assignee: | Markus Mohrhard <markus.mohrhard> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | cno, LibreOffice |
Version: | 3.3.0 release | ||
Hardware: | Other | ||
OS: | Windows (All) | ||
See Also: | https://issues.apache.org/ooo/show_bug.cgi?id=118863 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 45916 | ||
Attachments: | Bug 45925 - WinDbg session |
Description
Rainer Bielefeld Retired
2012-02-11 03:46:53 UTC
@Markus: Please feel free to reassign (or reset Assignee to default) if it’s not your area. Please set Status to ASSIGNED if you accept this Bug. Created attachment 64017 [details] Bug 45925 - WinDbg session Checked with: LO 3.5.5.3 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Well, selecting a column means that the content will be copied to >1 M rows. It can take time and LO is unresponsive. So it is more like bug 48381. Additionally, LO crashed while autosave in my case. I made memory dump and processed it with WinDbg. Attached full WinDbg session with memory dump file loaded. fixed with http://cgit.freedesktop.org/libreoffice/core/commit/?id=6b8704d974abd4ab7fb58036a961fa0b7136aaa7 ? Just for the records, followed-up with http://cgit.freedesktop.org/libreoffice/core/commit/?id=6b8704d974abd4ab7fb58036a961fa0b7136aaa7 http://cgit.freedesktop.org/libreoffice/core/commit/?id=6b8704d974abd4ab7fb58036a961fa0b7136aaa7 grml.. and that instead was http://cgit.freedesktop.org/libreoffice/core/commit/?id=57b8e7c96bafb97f881b7db73624693392e13540 http://cgit.freedesktop.org/libreoffice/core/commit/?id=8fd7a53d3cf1ed788c705cafb443801203787c9d A remaining bottle neck seems to be cell insertion. |
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.