D’oh!

Posted by Kim Kalland on July 6, 2010 · 18 comments

We screwed up! A serious bug in Qt 4.6.3′s QtOpenGL module on Windows went undetected through reviewing, the auto-test system and quality assurance! The bug causes a device context leak, and after 9999 repaints, the program stops updating its widgets. The bug is fixed in our repositories and will not appear in our next releases. Until then, if you are compiling Qt from source, you can use the this patch.

QShare(this)

No related posts.


18 comments

1 scorp1us July 6, 2010 at 2:31 pm
 

epositories and will not appear in our next releases.

‘not’ or ‘now’?

2 Fazer July 6, 2010 at 2:46 pm
 

And what about people using Qt from binaries? Will you release a fixed version of Qt 4.6? Or maybe Qt 4.7 is going to come out so soon that it makes no sense for you to include the fix in the earlier versions?

3 anon July 6, 2010 at 4:26 pm
 

What is happening to Trolls? 2 fails in a row already. Are trolls turning in corporate programmers?

4 The Eye July 6, 2010 at 4:34 pm
 

“and will *not* appear in our next releases”?? (emphasis added)

5 Daniel Molkentin July 6, 2010 at 4:46 pm
 

Yes, the bug has been fixed, hence it won’t appear in the next releases.

6 scorp1us July 6, 2010 at 4:57 pm
 

Qt’s open GL never worked on my ATI hardware anyway. Nvidia is fine.

7 scorp1us July 6, 2010 at 4:58 pm
 

OOOh. We don’t talk about bugs, talk about the fix. Say: “The Fix WILL appear”. It is confusing otherwise?

8 detro July 6, 2010 at 6:00 pm
 

@anon: Come on. The guys are working like hell, “errare umanum est”.

9 Donald Carr July 6, 2010 at 7:35 pm
 

@kkalland: Good on you for getting this adequate external visibility

Clearly now that we have caught this bug, subsequent releases will be free of it. The take away is that if you are using Qt 4.6, you should ideally be using a daily refreshed Qt checkout from the gitorious repo, which is a standing patch release against the latest and greatest stable Qt release.

10 NuShrike July 6, 2010 at 9:52 pm
 

Why not just release a 4.6.3_1 patch-up (like FreeBSD does), or 4.6.4 if you really have to?

11 AlekSi July 7, 2010 at 12:03 am
 

Don’t worry guys, Rails 2.3.6, .7, .8 were released in 3 days. :D

12 gordin July 7, 2010 at 7:33 am
 

Is this bug in 4.6.2 as well? We are seeing problems in our software that may be caused by this bug but we are still using 4.6.2.

13 gordin July 7, 2010 at 8:43 am
 

I checked myself: bug was introduced in 4.6.3 and is not in 4.6.2

14 l0calh05t July 7, 2010 at 11:11 am
 

Since we’re already on the topic of OpenGL, what about http://www.qtforum.org/article/32627/opengl-paint-engines-broken.html ?

15 Ivan July 7, 2010 at 7:36 pm
 

Guys, you really annoing by repeatadly broking OpenGL since Qt 4.6 release. Does QA service need some improvements, not?
And yes, Qt4 OpenGL does not work normally on my ATi linux hardware, however the TuxKarts works!

16 Donald Carr July 7, 2010 at 7:59 pm
 

@l0calh05t:

http://bugreports.qt.nokia.com/secure/Dashboard.jspa

We have a centralized bug reporting system which gives us some infrastructure to verify, prioritize and track issues, please utilize it. Apart from the fact it is entirely off the radar, it looks like a good solid bug report.

17 Max Waterman July 11, 2010 at 10:21 am
 

> went undetected through reviewing, the auto-test system and quality assurance

I see no mention of improving your auto-test system/etc – at least you can add a test so that this bug doesn’t reappear in future.

18 omynos July 12, 2010 at 1:28 pm
 

Man, you guys are getting just hassled over this… I feel bad for you. It’s great software still, these things are bound to happen.

Comments on this entry are closed.

Previous post:

Next post: