Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index


Hello,

During QA activity, I've noticed more and more bugs (including about crash) which involved OpenGL. In general, I advise to upgrade graphic driver first, then ask to provide opengl_device.log if the bug is still reproduced.

But there's also perf pb (see tdf#101162), whereas it should be bring better perfs.

So here are some questions about OpenGL part in LO:

1) Are there people which may help/put on cc about these bugs?

I found no one on https://wiki.documentfoundation.org/FindTheExpert

2) What about graphic card driver version/env blacklist politics?

I mean, I pushed this patch https://cgit.freedesktop.org/libreoffice/core/commit/?id=ecaabbf527f6f6207ce1ca8924708d23e6db45f5

(blacklist Intel HD Graphics 630 for non minimal version)

and there's another one in review (https://gerrit.libreoffice.org/#/c/49186/) which would blacklist completely the graphic card since even with the last version of graphic card driver, it crashes.

Should these blacklist items must regularly reviewed and so we should ping reporters to know if it's better with a graphic card driver upgrade?

Eg: once a year, ping reporters and ask them to upgrade their driver and give a new try?

I don't think it's realistic but don't know how to deal with this.

3) crashreports may show opengl part but how to know if it's due to a buggy driver or due to OpenGL implementing LO part?

Julien


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.