Clone of bug 95573 When attempting to update an installed extension via the Extensions Manager GUI, LO hangs on OSX
Created attachment 123182 [details] SAL LOG debug bt
Interesting log. How long did you leave it before exiting ? 3564 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 17 and has active idles 3565 info:vcl.schedule:45624:17:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 12 and no idles 3566 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8575 and has active idles 3567 info:vcl.schedule:45624:17:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8575 and no idles 3568 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8573 and no idles 3569 info:vcl.schedule:45624:17:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8572 and no idles 3570 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8572 and no idles 3571 info:vcl.schedule:45624:17:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8572 and no idles 3572 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8571 and no idles 3573 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8571 and no idles 3574 info:vcl.schedule:45624:17:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8571 and no idles 3575 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8571 and no idles 3576 info:vcl.schedule:45624:17:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8569 and no idles 3577 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8568 and no idles 3578 info:vcl.schedule:45624:17:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8568 and no idles 3579 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8567 and no idles 3580 info:vcl.schedule:45624:17:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8567 and no idles 3581 info:vcl.schedule:45624:1:vcl/source/app/scheduler.cxx:268: Calculated minimum timeout as 8567 and no idles It seems like there is no busy idle handler at the end anyway. Did you leave this for around 20 minutes before force killing it ? =) If so - then (I guess) we are going to need a series of back-traces with all symbols for this; it doesn't look like a busy-loop. Thanks !
Hmm don't remember exactly how long, possibly at least 15min, I had nothing else runnning on that machine :)
The bug is older than 5.2 it's present in 4.4.5
Same bug here: https://bugs.documentfoundation.org//show_bug.cgi?id=70607 *** This bug has been marked as a duplicate of bug 70607 ***
Have run this up to 30 minutes with no change.