(Update: This problem has been partially worked around, see the later post on 1.3.0)
(Update 2: I have traced this back to the specific change in Firefox 83 that caused the issue and have posted an issue on Mozilla's bug tracker. Please be aware that given the nature of the commit that caused the issue, it's possible that fixing the issue experienced by Wingman Jr. may cause other things to break - so fixing this may not be as easy as it seems.)
(Update 3: I have found a technical workaround and have a full fix in progress - here's the post explaining the changes.)
Today my browser updated itself to Firefox 83, and it promptly made the addon on unusable! The underlying issue is something related to the way the graphics card, Firefox 83, and possibly Tensorflow.js are interacting. Note this may not affect all users but if suddenly performance became unusable after Firefox updated itself, this is why.
Workaround: Revert back to Firefox 82; otherwise the performance was poor enough you may have to disable the plugin until this can be resolved.
Things I thought might help, but did not:
- Updating graphics driver
- Reverting to an old version of Tensorflow.js. This also means older versions of the addon are unlikely to work either.
Technical details can be found with the bug I am tracking for this.
Sorry for the inconvenience!
No comments:
Post a Comment