Created attachment 68279 [details] File with Pivot Table I use three operating systems: Ubuntu, HP and windose windose 7. This crash only occurs under the operating systems windose. When you create a pivot table, I, first of all, to define a range of table cells with the first line, which contains the names of the data fields. Next, I go to the menu "Data - DataPilot - Create." The dialog box "Select Source", in which I leave selected the "Current Selection" and click "OK". After I move the buttons with the names of the data fields on all four counts and doing it fast enough, then adjust the placement of buttons, dragging some of the buttons from one unit to another. At some point, the program terminates and Tsalts dialog box appears on the emergency stop with a proposal to restore the working file. In this case, the button "OK" is not pressed, ie dialog box hangs. In the future, only helps the "Task Manager windose" to close the process.
I use three operating systems: Ubuntu, Windows XP and Windows 7. This crash only occurs under the Windows operating systems. When I create a pivot table, first of all, I define a range of table cells with the headers, which contains the names of the data fields. Next, I go to the menu "Data - Pivot Table - Create." The dialog box "Select Source", in which I leave selected the "Current Selection" and click "OK". After that, I drag the buttons with the names of the data fields on all four areas and doing it fast enough, then adjust the placement of buttons, dragging some of the buttons from one area to another. At some point, the program terminates and dialog box appears on the emergency stop with a proposal to restore the working file. In this case, the button "OK" is not valid and dialog box hangs. To decide this problem, only helps the "Windows Task Manager" to close the processes soffice.bin and soffice.exe.
NOT reproducible with Server Installation of "LibreOffice 3.6.2.2 release German UI/ German Locale [Build-ID: da8c1e6] on German WIN7 Home Premium (64bit) @Sergey: We need a step by step instruction containing every key press and every mouse click showing a way how to reproduce the crash reliably
Ok! I've made "how to" video to explain all steps and reproduce this Crash. You may see it from this link: http://www.screencast.com/t/DtQts6kI
Hello Verified with Windows 7 64bits & Windows XP with LibO - 3.6.2.1 - 3.6.3.2 (Build ID: 58f22d5) - 3.6.4.0+ (Build ID: b1f308d) Other steps to reproduce: 1. File> New> Spreadsheet 2. Data> Pivot table> Create 3. Data source registered > Ok 4. Base: Bibliography, Source: biblio, Type: Sheet> Ok 5. Layout: Row field - Publisher, Data Field - Identifier 6. Drag "Publisher" from Row field to Column field Crash + You have to kill the process Regards Pierre-Yves
Hello Sorry, but not reproducible (neither Sergey steps nor Pierre-Yves steps) on French Win 7 Pro 64bits with - Version 3.6.2.2 (Build ID: da8c1e6) French UI - Version 3.6.3.1 (Build ID: f8fce0b) test version install in server mode Perhaps something related to antivirus ? , java (1.7.0_09 for me ) ? language (but I think pierre-yves has french version) ? other options ? Regards,
Hello! At home notebook - WinXP Pro 32-bit (Russian) with Java 1.6, no antivirus. On my working place - Win7 Home Premium 64-bit (Russian) with Java 1.7, Kaspersky Antivirus 6.
I can confirm this on Win7, LibreOffice 3.6.3.2. Practically, it always crashes when you leave column or row fields empty (after having assigned some fields to them before). Will check on Linux in the evening. This is quite disturbing and one of the few reasons we have not switched to 3.6.X at work (with my glorious exception ;-)).
and Java 1.6.0_37, No on access antivirus, Clamwin on demand antivirus (the deamon is running though), USEnglish and Greek UI (both crash). Reproducible on every single pivot I tried (if I leave "row fileds" or column fields" empty, after having previously assigned them fields).
No matter how many times I try, on Windows, following the same exact steps as the video shows, I cannot reproduce the crash.
That is strange. Btw in Linux I don't have the problem (checked 64bit versions of 3.6.3.2 on two different OpenSuse installations and on Ubuntu 12.04 (the latter in vm). However, the problem on windows 7 persists (2 different installations). I will see how xp in vbox behaves...
Persists in 3.6.4.1
At this point someone who can replicate this needs to provide a stack trace in order for this to proceed. Without that we can't really try to even fix this.
bfoman is the heroic Windows stack-trace provider - can you help ? :-)
I can not reproduce it. Win 7x64 Ultimate LibreOffice Version 3.6.4.1 (Build ID: a9a0717) Java 1.7.09_32. I guess, an user profile reset has been done to verify the issue it is no there.
(In reply to comment #13) > bfoman is the heroic Windows stack-trace provider - can you help ? :-) If you want to get symbols then I can only check if this is reproducible on my 3.5.x debug build. W2008R2@20 is empty and I have serious issues with building both 3.6.x or master with symbols on my own.
After applying the latest updates on Win7 (KB2574819, KB2592687) I do no longer have this problem. (which probably explains why you can not replicate the behavior). So, I can recommend to anyone encountering this really annoying bug, to install the above updates...
(In reply to comment #16) > So, I can recommend to anyone encountering this really annoying bug, to > install the above updates... I haven't the time to look at it yet but it would be very surprising if those KBs resolved the issue. 2574819 - An update is available that adds support for DTLS in Windows 7 SP1 and Windows Server 2008 R2 SP1 2592687 - Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1
The only changes I made, between having the bug and not having the bug were: 1. Those two updates and 2. A firefox update which probably has the same probability of being related as the other two. Maybe, I had not rebooted the PC after updating to LibreOffice 3.6.4.1 and checking that the bug persists (I can't recall), but that is something somebody else who still encounters the bug could easily check.
Checked with: LO 3.5.6.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit LO 3.6.3.2 Build ID: 58f22d5 Windows 7 Professional SP1 64 bit LO 3.7.0.0.alpha0+ Build ID: e12f501 Windows 7 Professional SP1 64 bit Could not reproduce. Those MS KBs seems to be irrelevant as I do not have them installed.
If nobody can reproduce this crash anymore can we close the bug report?
Sounds most sensible - no response this year -> worksforme - presumed fixed in an update. Thanks Markus ! :-)