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.
Build ID: 3bd8316718fdfed454c01a9c4ae6af6beb34437d
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2;
Locale: ca-ES (ca_ES.UTF-8); Calc: threaded
is the slowness reproducible using LibreOffice without procdump ?
I can't reproduce it in
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
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
> 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 :-)