<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Unary/Binary Operators glyph rendering initially misplaced" href="https://bugs.documentfoundation.org/show_bug.cgi?id=118884#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Unary/Binary Operators glyph rendering initially misplaced" href="https://bugs.documentfoundation.org/show_bug.cgi?id=118884">bug 118884</a> from <a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>And <a href="https://gerrit.libreoffice.org/#/c/60092/">https://gerrit.libreoffice.org/#/c/60092/</a> is just cleanup patch to get rid of a now duplicated HFONT life-cycle management. The original version had a bug. I couldn't debug it, because of a memory corruption unrelated to my patch, with very "funny" failing assertions. That resulted in <a href="https://gerrit.libreoffice.org/#/c/60162/">https://gerrit.libreoffice.org/#/c/60162/</a>. I just found two occurrences directly related to my failing unit test, but some grep found more and reviewing more code around the first hits revealed a lot more. And this is just the result from a straight-forward grep over the code base. Who knows how many of these std:unique_ptr<...[]> array delete[] bugs are still there undetected. I'm just wondering why none of our static analysis tool-chains caught these earlier... build without online-updater?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>