https://bugs.documentfoundation.org/show_bug.cgi?id=170544

Buovjaga <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ilmari.lauhakangas@libreoff
                   |                            |ice.org

--- Comment #2 from Buovjaga <[email protected]> ---
This sounds like bug 42673, but it is a very old known problem while you
describe it as a recent regression. If something actually regressed, you should
be able to perform binary bisecting to find out the exact cause.

https://wiki.documentfoundation.org/QA/Bibisect
https://wiki.documentfoundation.org/QA/Bibisect/Windows
https://bibisect.libreoffice.org/win64-25.8

1. Open Powershell 5
2. Give this command to install the latest Powershell: winget install --id
Microsoft.PowerShell --source winget
3. Give this command to install git: winget install -e --id Git.Git
4. Close the old Powershell window and use Windows Start Menu to launch
Powershell 7
5. Go to some directory, could be the root of C: drive itself, so `cd C:\` and
clone the 25.8 bibisect repository with: git clone
https://bibisect.libreoffice.org/win64-25.8.git
6. After the clone has finished, say cd win64-25.8
7. Now give these chained commands and check if it freezes: git checkout oldest
&& instdir\program\soffice
8. If it does not freeze, you should be able to bibisect the issue. Next use
this and hopefully it *will* exhibit the freeze: git checkout master &&
instdir\program\soffice
9. Next start the bibisecting with: git bisect start master oldest &&
instdir\program\soffice
10. Whenever you don't get the freeze say: git bisect good &&
instdir\program\soffice
11. Whenever you do see the freeze, say: git bisect bad &&
instdir\program\soffice
12. When the process is finished after something like 13 steps, it will display
the first bad commit. Select and copy all the lines in this final output (you
can copy by right-clicking, it gets put into the clipboard immediately) and
paste here to a comment for us to inspect.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to