# Can there be a "Known Issues or Bugs" Section to the Forum?

**URL:** <https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096>\
**Category:** Site Feedback\
**Tags:** obj-format, chromium, webkit, webgl\
**Created:** [July 13, 2024, 5:39am UTC](https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096 "2024-07-13T05:39:07Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![BrentBuffham](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/brentbuffham/32/43446_2.png) [@BrentBuffham](https://discourse.threejs.org/u/BrentBuffham)\
**Post date:** [July 13, 2024, 5:39am UTC](https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096/1 "2024-07-13T05:39:07Z")

</div>

Is it possible to have a known bugs section to the forum?  
Recently I had a display issue that I though was in my implementation however the case is that it is a known issue with MacOS chromium based browsers and meshes with more than 64K vertices, but not on WebKit browsers.

Affected MacOS Versions Browsers:

- Chrome
- Brave
- Edge
- Opera

Unaffected MacOS Browsers

- Safari
- Firefox
- DuckDuckGo

After days of searching:  
Chromium Issues has this Issue:  
[[Chromium](https://issues.chromium.org/issues/40223901)]([https://WEBGL](https://WEBGL) and Chromium Browsers on MacOS)

---

<div class="post-metadata">

**Author:** ![Lawrence3DPK](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/lawrence3dpk/32/29184_2.png) [@Lawrence3DPK](https://discourse.threejs.org/u/Lawrence3DPK)\
**Post date:** [July 13, 2024, 7:56am UTC](https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096/2 "2024-07-13T07:56:19Z")

</div>

[Issues · mrdoob/three.js · GitHub](https://github.com/mrdoob/three.js/issues) 🤔

If its confirmed to be a browser issue it’s best to also file a report with the respective provider(s)

---

<div class="post-metadata">

**Author:** ![PavelBoytchev](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/pavelboytchev/32/38639_2.png) [@PavelBoytchev](https://discourse.threejs.org/u/PavelBoytchev)\
**Post date:** [July 13, 2024, 9:45am UTC](https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096/3 "2024-07-13T09:45:58Z")

</div>

I think the essence of the proposal is not to report bugs, but to collect a list of issue. Three.js users that experience a problem may look up in this list and check whether their issue is a known problem or not. This might save a lot of efforts and frustration.

---

<div class="post-metadata">

**Author:** ![electric.cicada](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/electric.cicada/32/34971_2.png) [@electric.cicada](https://discourse.threejs.org/u/electric.cicada)\
**Post date:** [July 13, 2024, 10:05am UTC](https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096/4 "2024-07-13T10:05:05Z")

</div>

I second the motion, it would be definitely helpful.  
I’m also struggling with a similar issue atm, but it’s more like a Mac vs Windows issue, and it might be a known one, I just can’t seem to find it anywhere.

---

<div class="post-metadata">

**Author:** ![BrentBuffham](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/brentbuffham/32/43446_2.png) [@BrentBuffham](https://discourse.threejs.org/u/BrentBuffham)\
**Post date:** [July 13, 2024, 7:11pm UTC](https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096/5 "2024-07-13T19:11:56Z")

</div>

Correct. just a place to have known issues if they belong to another provider and known bugs if they belong to threejs.

---

<div class="post-metadata">

**Author:** ![BrentBuffham](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/brentbuffham/32/43446_2.png) [@BrentBuffham](https://discourse.threejs.org/u/BrentBuffham)\
**Post date:** [July 13, 2024, 7:14pm UTC](https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096/6 "2024-07-13T19:14:03Z")

</div>

Copy… I reported it to Chromiun _its been an issue since 2019… but not with Webkit._

---

<div class="post-metadata">

**Author:** ![manthrax](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/manthrax/32/2596_2.png) [@manthrax](https://discourse.threejs.org/u/manthrax)\
**Post date:** [July 14, 2024, 12:12am UTC](https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096/7 "2024-07-14T00:12:39Z")

</div>

Every GPU manufacturer has their own drivers.

Intel and qualcomm drivers are notoriously buggy. Intel has been getting better over the years. ATI’s drivers are pretty good… NVidia drivers are the most compatible, although almost to the opposite extreme in that they will proactively put fixes in their drivers to “fix” issues with devs doing unsupported or underspecified operations.

It would be nice if there was a database of “these things are broken” but creating such an artifact is a Ton of work, and these bugs get fixed over time, and new ones crop up, so its a never ending process.

You can grind your fingers down trying to work around issues like this, or you can just check the GPU string and blacklist them from your app, and show them a mp4 instead with a label like “Driver XYZ has a known issue and is not supported by this app.” and move on with your life.  
The more hoops you go through to work around the issues, the more you relieve the pressure on manufacturers to fix their drivers.  
I know this isn’t super helpful advice, but I just want to give some perspective.

Here’s a code snippet which may tell you what driver is actually in play while your app is running, and perhaps can be something to key different behaviors under different circumstances.

```javascript
function getWebGLRendererInfo() {
    // Create a canvas element to initialize WebGL context
    var canvas = document.createElement('canvas');
    var gl = canvas.getContext('webgl') || canvas.getContext('experimental-webgl');

    if (!gl) {
        console.log('WebGL not supported');
        return;
    }

    // Access the WEBGL_debug_renderer_info extension
    var debugInfo = gl.getExtension('WEBGL_debug_renderer_info');

    // If the extension is available, extract the GPU and driver information
    if (debugInfo) {
        var vendor = gl.getParameter(debugInfo.UNMASKED_VENDOR_WEBGL);
        var renderer = gl.getParameter(debugInfo.UNMASKED_RENDERER_WEBGL);
        console.log('GPU Vendor: ', vendor);
        console.log('GPU Renderer: ', renderer);
    } else {
        console.log('Unable to access WebGL debug renderer info.');
    }
}

getWebGLRendererInfo();

```

---

<div class="post-metadata">

**Author:** ![Lawrence3DPK](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/lawrence3dpk/32/29184_2.png) [@Lawrence3DPK](https://discourse.threejs.org/u/Lawrence3DPK)\
**Post date:** [July 14, 2024, 8:52am UTC](https://discourse.threejs.org/t/can-there-be-a-known-issues-or-bugs-section-to-the-forum/68096/8 "2024-07-14T08:52:35Z")

</div>

> [@PavelBoytchev](#):
>
> but to collect a list of issue.

> **[Quickstart for GitHub REST API - GitHub Docs](https://docs.github.com/en/rest/quickstart?apiVersion=2022-11-28&tool=curl)**
>
> Learn how to get started with the GitHub REST API.

the github api is a way to get a list of all the issues of a given repo, the result can be filtered and organized however you wish really, I personally like ven diagrams. I would also say that having a source of truth to all existing issues as well as closed outdated ones should ideally all be kept in one place for devs to look into and fix, github issues is the ideal way of managing this and attaining this data through the provided api is the _only_ real way of clinically consuming this real time data, otherwise as @manthrax has outlined, this will quickly become a never ending nightmare project to maintain…

**EDIT:**

> [@BrentBuffham](#):
>
> known issues if they belong to another provider and known bugs if they belong to threejs.

This is also achievable through using the github api as you could get all issues tagged webgl / three js from all the necessary providers repos and create an automated framework to categorise and cross reference issues from all sources, again, without an appropriate framework in place that will heavily automate this, it seems like a burden for what it’s worth…