Steps hos to reproduce with "LibreOffice 3.5.0 RC3 German UI/Locale [Build-ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735] on German WIN7 Home Premium (64bit):
1. Start Calc, and new a spreadsheet document.
2. Merge cell A1 and B1.
3. Input data to cell A1, A2 and B2
4. Copy cells A1: B2
5. Click column header to select the whole column, e.g. Column E.
6. Paste cells copied in step 4
Expected: all column filled with contents
[Reproducible] with "LibreOffice 3.4.5 German UI [Build ID: OOO340m1 (Build:502)]" parallel Server installation on German WIN7 Home Premium (64bit)
[Reproducible] with "LibreOffice Portable 3.3.0 - WIN7 Home Premium (64bit) German UI [OOO330m19 (Build:6) tag libreoffice-220.127.116.11]"
Also reproducible with OOo 3.3, so problem seems inherited from OOo.
Works fine with OOo 3.1.1
NEW due to own test results and referenced AOOo Issue "[From Symphony] Calc stop responding if paste merged celss to a column"
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
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.
Just for the records, followed-up with
grml.. and that instead was
A remaining bottle neck seems to be cell insertion.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.2 or later)
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Win 7 Pro 64-bit Version: 18.104.22.168.alpha1+
Build ID: 3ecef8cedb215e49237a11607197edc91639bfcd
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-19_23:16:58
Locale: fi-FI (fi_FI)
On pc Debian x86-64 with master sources updated yesterday, I could reproduce the hang.
Created attachment 125338 [details]
bt at random
I attached a bt at random
Setting Assignee back to default. Please assign it back to yourself if you're
still working on this issue
Repro in 6.1+
Repro 6.2+ in Windows.