Description: A python code process being active on file open (and using quite some CPU time) (triggered by linguistic_DicList_get) Steps to Reproduce: 1. Install verysleepy or another profiler (or more basic, the task manager 2. Open the attached file 3. Notice CPU keeps running for 30 seconds or so (with verysleepy you can see it being python process Actual Results: LibreOffice is primarily C++, so unsure what the Python code is doing. PyDict_GetItem python38 PyRun_FileExFlags python38 PyRun_FileExFlags python38 PyRun_StringFlags python38 PyAST_Optimize python38 PyCFunction_DebugMallocStats python38 PyOS_URandomNonblock python38 PyEval_GetFuncDesc python38 PyEval_EvalFrameDefault python38 PyObject_Call python38 PyFunction_Vectorcall python38 PyOS_URandomNonblock python38 PyEval_GetFuncDesc python38 PyEval_EvalFrameDefault python38 PyObject_Call python38 PyFunction_Vectorcall python38 PyCell_Set python38 PyMethod_Self python38 PyVectorcall_Call python38 PyInit_pyuno pyuno [00007FFCF1EC28AC] mscx_uno [00007FFCF1EC2D47] mscx_uno [00007FFCF09E3EEA] invocadaptlo [00007FFCF09E4361] invocadaptlo uno_ext_getMapping mscx_uno uno_ext_getMapping mscx_uno uno_ext_getMapping mscx_uno linguistic_DicList_get_implementation mergedlo osl_getTempDirURL sal3 Expected Results: I don't think Python code should be called Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.0.0.alpha1+ (x64) / LibreOffice Community Build ID: b2467d6c7af988f8ed4e090ebf9472be6c84fb06 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL
Created attachment 180212 [details] Example file
The is slightly reduced file: original at attachment 159685 [details]
Original file at bug 119148 (attachment 144018 [details])
@Noel, My mistake, sorry
Opens fine with 7.2 oldest.. crashing at 7.2 master (and keeps crashing) It's the same file as for bug 148913, so might be that both issues having the same root cause
(In reply to Telesto from comment #5) > It's the same file as for bug 148913, so might be that both issues having > the same root cause Bug 148913 has ben fixed meanwhile, could you please restest? => NEEDINFO Can't see any CPU problem in Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp