https://bugs.freedesktop.org/show_bug.cgi?id=75380
--- Comment #3 from Niklas Johansson <[email protected]> --- I used bibisect and ended up at the following two commits. prevent some implicit iterator conversions http://cgit.freedesktop.org/libreoffice/core/commit/?id=e79c706ddda21f850fe3c5a867bacf3982e5b112 GPU Calc: add an inline function to legalize inputs for reduction. http://cgit.freedesktop.org/libreoffice/core/commit/?id=d7e4e5d35e66dbfcc30576d198e393661d84f616 Looking deeper into the git history around that time a lot of changes was pushed to the chart area: http://cgit.freedesktop.org/libreoffice/core/log/?id=3b2b516ce0fee9bc609f4213affa5b0a71f08cb1&qt=range&q=3b2b516ce0fee9bc609f4213affa5b0a71f08cb1 Would it make sense for me to do some manual builds around that time to try to narrow in on when the issue was introduced or is that just a waste of my time? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
