https://bugs.documentfoundation.org/show_bug.cgi?id=172341
--- Comment #16 from [email protected] --- (In reply to Xisco Faulí from comment #15) > (In reply to support from comment #10) > > I reproduced this on Linux using: > > > > | G_SLICE=always-malloc MALLOC_CHECK_=3 MALLOC_PERTURB_=165 > > SAL_USE_VCLPLUGIN=gtk3 ./soffice > > > > in the bibisect repository: linux-64-25.8 > > > > Here are the results: > > > > Repository linux-64-25.2: > > Master | good | 93c0688bd7df1ab48888d28068b49a902c364d51 2025-11-02 12:50:14 > > +0100 > > Oldest | good | 36d42743a6445f6e5160135dc8eca2326ee8e127 2024-06-18 18:20:57 > > +0200 > > > > Repository linux-64-25.8: > > Master | bad | f8b367c9aa3aa7b06882b1a210fd3240c622c29e 2025-11-26 20:32:26 > > +0100 > > Oldest | bad | e16481e476e67e78cca4b4fd369bb92665629d1a 2025-11-19 21:11:02 > > +0100 > > if I understand it correctly, you can reproduce the issue with the oldest > commit from linux-64-25.8 but not with the newest of linux-64-25.2? Correct - but linux-64-25.2 does not contain all commits between linux-64-25.2 and linux-64-25.8. > That indicates something is odd, since the oldest of linux-64-25.8 should be > older than the newest of linux-64-25.2. Agree. > > Besides, where is the (In reply to support from comment #10) > > I reproduced this on Linux using: > > > > | G_SLICE=always-malloc MALLOC_CHECK_=3 MALLOC_PERTURB_=165 > > SAL_USE_VCLPLUGIN=gtk3 ./soffice > > > > in the bibisect repository: linux-64-25.8 > > > > Here are the results: > > > > Repository linux-64-25.2: > > Master | good | 93c0688bd7df1ab48888d28068b49a902c364d51 2025-11-02 12:50:14 > > +0100 > > Oldest | good | 36d42743a6445f6e5160135dc8eca2326ee8e127 2024-06-18 18:20:57 > > +0200 > > > > Repository linux-64-25.8: > > Master | bad | f8b367c9aa3aa7b06882b1a210fd3240c622c29e 2025-11-26 20:32:26 > > +0100 > > Oldest | bad | e16481e476e67e78cca4b4fd369bb92665629d1a 2025-11-19 21:11:02 > > +0100 > > if I understand it correctly, you can reproduce the issue with the oldest > commit from linux-64-25.8 but not with the newest of linux-64-25.2? > That indicates something is odd, since the oldest of linux-64-25.8 should be > older than the newest of linux-64-25.2. Please, look at #Comment 12 - repo linux-64-25.2 is missing linux-64-25.2.x branches. So there is gap between commits. > Can you give it a try with > https://bibisect.libreoffice.org/linux-64-releases ? Look like no 25.x nor 26.x in this repo: $ git clone https://bibisect.libreoffice.org/linux-64-releases.git $ cd linux-64-releases $ git log --oneline --all 9c4b0c1408 (HEAD -> master, tag: libreoffice-24.8.7.2, origin/master, origin/HEAD) libreoffice-24.8.7.2 0901aa443c (tag: libreoffice-24.8.7.1) libreoffice-24.8.7.1 a505393c01 (tag: libreoffice-24.8.6.2) libreoffice-24.8.6.2 ff38bf0232 (tag: libreoffice-24.8.6.1) libreoffice-24.8.6.1 b6ad0ff6ca (tag: libreoffice-24.8.5.2) libreoffice-24.8.5.2 d8600a496f (tag: libreoffice-24.8.5.1) libreoffice-24.8.5.1 30cfff17cb (tag: libreoffice-24.8.4.2) libreoffice-24.8.4.2 60f5b8ca40 (tag: libreoffice-24.8.4.1) libreoffice-24.8.4.1 a49ef0d8a5 (tag: libreoffice-24.8.3.2) libreoffice-24.8.3.2 698b1cefe1 (tag: libreoffice-24.8.3.1) libreoffice-24.8.3.1 dd7d48e20b (tag: libreoffice-24.8.2.1) libreoffice-24.8.2.1 2671523e5d (tag: libreoffice-24.8.1.2) libreoffice-24.8.1.2 8369698f0e (tag: libreoffice-24.8.1.1) libreoffice-24.8.1.1 5568cb6737 (tag: libreoffice-24.8.0.3) libreoffice-24.8.0.3 1b11b72921 (tag: libreoffice-24.8.0.2) libreoffice-24.8.0.2 5f76c435db (tag: libreoffice-24.8.0.1) libreoffice-24.8.0.1 53c35a8f7f (tag: libreoffice-24.8.0.0.beta1) libreoffice-24.8.0.0.beta1 1c70c8fac9 (tag: libreoffice-24.8.0.0.alpha1) libreoffice-24.8.0.0.alpha1 > > > > According to the core repository, there are 500 commits between these two > > repositories, which is why I was unable to bisect the regression using the > > available bibisect repositories > > Where is 500 commit from? at least from me, git log --oneline > 798b43c4ef433d9f2cbfa431ebdf9ec35c3b8a39.. > d28ca0db5edd43b9e2bb82d78021b4c4eb276d4e | wc -l returns 5629 Please, try to find for example commit "03322cb8279b26a9c1ab9c660b1eb7ed9187a851" in any bibisect repo. It is on git in branch 25.2.7 but not in bibisec linux-64-25.2: | https://gerrit.libreoffice.org/c/core/+/192906 | https://git.libreoffice.org/core/+/03322cb8279b26a9c1ab9c660b1eb7ed9187a851 -- You are receiving this mail because: You are the assignee for the bug.
