This bug is FILEOPEN that refers to FILESAVE Bug 118662 and attachment 143423 [details]. What I do is: 1. run LO (Home, Start?) for the first time, without any application 2. run procdump 3. File-open attachment 143423 [details]. 4. See that fileopen procdump happens. Procdump command, for any single loaded LO: path\SYSINTERNALSSUITE\procdump.exe soffice.bin -h "path\soffice.bin.dmp" I noticed the first time fileopen with some LO version is longer than on subsequent loads, like 25 secs vs. 5 secs. There is no dump on multiple fileopen and filesave actions when LO is already loaded. I don't have a good experience with fixing reported dumps, but let's try.
in Version: 6.2.0.0.alpha0+ Build ID: 3bd8316718fdfed454c01a9c4ae6af6beb34437d CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: threaded it takes real 0m6.335s user 0m6.714s sys 0m0.879s is the slowness reproducible using LibreOffice without procdump ?
I can't reproduce it in Versión: 6.1.0.3 Id. de compilación: efb621ed25068d70781dc026f7e9c5187a4decd1 Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group threaded either...
Let's all test this as a first test after computer start, since results differ.
Created attachment 144538 [details] BT from dump Maybe bug 117936 (no quite sure)
Since Telesto also had dump, I'll set to New. I modified the title to emphasize dump. Telsto's backtrace has vcllo!TabitemValue::isRightAligned+c2e9 and mine vcllo!weld::Builder::weld_metric_spin_button+14417 Can't say why they differ. I repro dump with yeterday's 6.2+ but also with 6.1 and at 4.3. Not with 4.2.7. Didn't compare dump reports.
(In reply to Timur from comment #5) > Since Telesto also had dump, I'll set to New. I modified the title to > emphasize dump. > Telsto's backtrace has vcllo!TabitemValue::isRightAligned+c2e9 and mine > vcllo!weld::Builder::weld_metric_spin_button+14417 > Can't say why they differ. > I repro dump with yeterday's 6.2+ but also with 6.1 and at 4.3. Not with > 4.2.7. Didn't compare dump reports. I'm tempted to add Caolán to the loop; because of all his welding... Looking at (vcllo!weld::Builder::weld_metric_spin_button) & TabitemValue::isRightAligned (which seems to be about the widget position: https://opengrok.libreoffice.org/xref/core/include/vcl/salnativewidgets.hxx#386 and seeing this similar behaviour loop endlessly in VerySleepy for attachment 144526 [details] when saving the file (does also dump a lot). Which seems odd to me. Why processing dialog stuff while saving? However, I'm not qualified to analyse or judge BT's :-)
Dear Timur, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Repro 7.1.0, no repro 7.2+ Windows. Looks ok, I cannot bibisect.