This is not directly related, but that it is why I thought it was a Qt bug. It it so easy in OpenGL to use badly API and having a good result that will work on almost all configurations.
Dislike in Vulkan there is no way to check if APIs are correctly used, so when we test our engine we can't really expect that it will run everywhere just because it runs on our computer. Anyway I had report the issue to Nvidia. 2017-04-21 15:09 GMT+02:00 Viktor Engelmann <viktor.engelm...@qt.io>: > I'm not an OpenGL expert, so this might be completely unrelated, but this > reminded me of > > http://lists.qt-project.org/pipermail/interest/2016-October/025009.html > > > On 21.04.2017 14:51, Xavier Bigand wrote: > > Hi Oliver, > > All other applications that crash at startup on the hardware on which we > also have the issue are made with Qt, games and all other applications are > running fine. > We finally found that it is specific to the latest Nvidia driver 381.65 > and at least geforce 1070 and 1060, we have tested on an other computer > with a 1080 and the same driver version that doesn't have the issue. > > OpenGL Nvidia drivers often crash with bad inputs, and you are right it is > boring because in this case we can't use Nsight or other things to debug. > > There is a lot of wrong OpenGL commands that can generate a good result > depending on drivers and hardware. This is the case with FBO on that we can > read and write at the same time with Nvidia and AMD GPUs, but not with > Intel ones. I think that is because Nividia or AMD have some code that fix > some common wrong commands in their driver to make OpenGL easier to use. > > I will fill a bug to Nvidia. > > Thank you all. > > > 2017-04-21 12:59 GMT+02:00 Till Oliver Knoll <till.oliver.kn...@gmail.com> > : > >> >> >> > Am 20.04.2017 um 21:04 schrieb Xavier Bigand <flamaros.xav...@gmail.com >> >: >> > >> > It is not necessary a bug from Nvidia, it can comes from bad parameters >> to functions like glDrawElements. Nividia drivers don't check a lot the >> parameters and given wrong values can cause buffer overflows,... >> >> Still a bug in nVidia code then. Again, an OpenGL driver is *not* >> supposed to crash, even with bad input. That's what the OpenGL standard >> mandates... >> >> And buffer overflows, God beware :) Report this to nVidia asap (you might >> get a reward for discovering a security hole ;)). >> >> Cheers, >> Oliver >> _______________________________________________ >> Interest mailing list >> Interest@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest >> > > > > -- > Xavier > > > _______________________________________________ > Interest mailing > listInterest@qt-project.orghttp://lists.qt-project.org/mailman/listinfo/interest > > > -- > > Viktor Engelmann > Software Engineer > > The Qt Company GmbH > Rudower Chaussee 13 > D-12489 Berlin > viktor.engelm...@qt.io+49 151 26784521 <+49%201512%206784521> > http://qt.io > Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho > Sitz der Gesellschaft: Berlin > Registergericht: Amtsgericht Charlottenburg, HRB 144331 B > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > > -- Xavier
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
