Created attachment 114858 [details] It is the problematic workbook. Dear Developers! After upgrading to 4.4.2.2 LO Calc starts to crash any time I open my workbook. One of the columns (BP) may calculate a BASIC function (DELTAT1) that solves an equation (Dteqn). This procedure is not so quick but before upgrading it was not cause any problem. Now it crashes after opening. No messages running LO from a terminal. For the test I include LOG file recording to the basic code (commented in the attachment. Please open LO Basic and uncomment if You want to create it. Tested on Ubuntu. The destination folder is the home folder). The behavior is unusual. It runs my solver (Deltat1) first time, performs only 2 iterations and run the solver again for a different cell. The second level run performs all required iterations, find a solution and returns. But the first run does not continue and LO Calc crashes without any message or APPORT call. I found only one workaround. Open this workbook and disable macros. Edit the module and cut-paste it to a text file. Save and close. Open it, enable macros. Because of missing macros some cells contain errors. Edit the module and past the code back. Manually edit cells in BP column to add and remove a space in the formula. It performs without any error. After that I can open the workbook only some times. And the problem reappears... How to reproduce 1. Save and close all documents (if opened)!!! 2. Run the attached workbook. Enable macros. If this bug affect You the LO Calc will close. Tested on Lenovo Ideapad Z580A with Core I7 processor 2,9 GHz.
Created attachment 114859 [details] THis is my LOG. The first number of any line is the run idintifier and the Level is the level of the run.
I can not confirm with Version: 4.5.0.0.alpha0+ Build ID: 51e0d789c344547956764c3b5f0ef5a304f4e0aa TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-04-13_16:58:45 No crash when open file, macros enabled.
Tested on Windows 8.1. Version 4.4.1.2 - No crash Version 4.4.2.2 - No crash
(In reply to Viktor Mileikovskyi from comment #3) > Tested on Windows 8.1. > Version 4.4.1.2 - No crash > Version 4.4.2.2 - No crash Maybe you should try renaming your user profile in your Linux system: https://wiki.documentfoundation.org/User_Profile#Resolving_corruption_in_the_user_profile Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
I have 5 different user profiles for multiple instances of LO. When I delete the corresponding.lock file (after the previous crash) and open the test.ods from a different profile it cause the same crash.
(In reply to Viktor Mileikovskyi from comment #5) > I have 5 different user profiles for multiple instances of LO. When I delete > the corresponding.lock file (after the previous crash) and open the test.ods > from a different profile it cause the same crash. Please try with new profile. You can delete/rename profile, LO then create new one. After test you can give old profile back.
Created attachment 114979 [details] After user profile change Apport reports this information After user profile change apport tried to report the information in my attachment. The field "Unreportable reason" says in Ukrainian: "This package is not official. Please uninstall all non-official packages and try again"
Tested on LO 4.4.3.2 on Ubuntu. Before testing the user profile was deleted and automatically created by LO. After opening test.ods LO crashes without any message or APPORT activity.
(In reply to Viktor Mileikovskyi from comment #8) > Tested on LO 4.4.3.2 on Ubuntu. Before testing the user profile was deleted > and automatically created by LO. After opening test.ods LO crashes without > any message or APPORT activity. Maybe try getting a backtrace: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Documents created or saved on the new office version are free of the bug. To correct old document it is enough to open it, disable macros, change anything (for example add anything to an empty cell and remove it, don't undo) and save the document. After that the document will not cause the crash. Appear to be solved.
Thanks for testing, Viktor! I will set the status to WFM, as we don't know any commit that fixed the problem.