https://bugs.documentfoundation.org/show_bug.cgi?id=148913
Jan-Marek Glogowski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression By|Jan-Marek Glogowski | Keywords|bibisected, bisected, |bibisectRequest |regression | --- Comment #11 from Jan-Marek Glogowski <[email protected]> --- (In reply to Caolán McNamara from comment #8) > The crash is under windows, but the bisect points to code which isn't built > under windows so there might be some variability to this. Yup. And a non-symbol backtrace from an alpha build doesn't really help. I'll see, if I can update my Win symbol build this WE and if the STR still apply, we can get a BT or maybe even a fix. If someone wants to re-bibiset, just don't miss the previous attempts. (In reply to Telesto from comment #10) > I'm already seeing this in 7.2 (so BT stack(, I'm attempted a bibisect, but > took the wrong turn somewhere.. > > [d489a9e1ee6173b712de05bf9a733ad9b394cfac] source > sha:1a984f2ff11e1125f146824924dcc373bccb0cdf > > is already crashing > > it might be > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=cb965f2cf6d68c284ccbd8a9635abfdfcc0538ca if i'm really close It seldomly happens that stuff breaks, is fixed and the broken again. That last commit is Writer code, so looks more promising. It might be closer to the real bug, but in the end a clear bt might help more, if bisecting results are varying. -- You are receiving this mail because: You are the assignee for the bug.
