Khronos public bugtracker – Most Frequently Reported Bugs

• Home
• | New
• | Browse
• | Search
• |
  [?]
• | Reports
• | Requests
• | New Account
• | Log In
  [x]
• | Forgot Password
  Login: [x]

What is this data?
Change parameters

Bug #	Dupe Count	Change in last 7 day(s)	Component	Severity	Priority	Target Milestone	Summary
52	3	0	Schema	trivial	P5	Release 1.5.0	Bugs in COLLADA 1.4.x that are duplicated in the internal (Khronos) Bugzilla
1272	2	0	glslang tracked on GitHub	normal	P3	---	__LINE__ directive must not be disabled.
410	2	0	Registry	normal	P3	---	Proposal for OES_standard_derivatives extension
367	2	0	Conformance Tests	major	P3	---	WFCT_Utils_testElementBooleanAttrib: incorrect checking of the return code

Change Parameters

Restrict to products:	COLLADA EGL glFX Khronos (general) KTX OpenCL OpenCL SPIR OpenGL OpenGL-ES OpenKODE OpenKOGS OpenMAX AL OpenMAX-IL OpenML OpenSL ES OpenVG OpenVX OpenWF SPIR-V WebCL WebGL
When sorting or restricting, work with:	entire list currently visible list
Max rows:
Change column is change in the last:	days
Open bugs only:

Or just give this to me as a . (Note: the order may not be the same.)

---

What are "Most Frequently Reported Bugs"?

The Most Frequent Bugs page lists the known open bugs which are reported most frequently, counting the number of direct and indirect duplicates of bugs. This information is provided in order to assist in minimizing the amount of duplicate bugs entered into Khronos public bugtracker, which saves time for Quality Assurance engineers who have to triage the bugs.

How do I use this list?

• Review the most frequent bugs list.
• If your problem is listed:
• Click on the bug number to confirm that you have found the same bug, and comment if you have additional information or move on with your testing of the product.
• If your problem not listed:
• Try and locate a similar bug that has already been filed.
• If you find your bug in Khronos public bugtracker, feel free to comment with any new or additional data you may have.
• If you cannot find your problem already documented in Khronos public bugtracker, file a new bug.