flathub / flathub/net.purrdata.PurrData

Use newer nw.js version

Open
#9 2 comments 0 reactions 0 assignees View on GitHub
waiting
Dominant language
Python
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

I'm seeing a continual issue with nw.js version 0.42.3, like `GetVSyncParametersIfAvailable() failed for 1561 times`. This seems to be https://bugs.chromium.org/p/chromium/issues/detail?id=879929.

When updating to nw.js version 0.42.6 things are even more broken: https://git.purrdata.net/jwilkes/purr-data/issues/572

Purr Data's Makefile still uses nw.js v0.24.4 (last minor release of the 0.24 series, from 25 Aug 2017). If the GetVSyncParametersIfAvailable() issue proves to be a problem then we might need to downgrade for now.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by inspecting the Purr Data Makefile entry that pins nw.js v0.24.4, then compare the reported behavior with nw.js 0.42.3 and 0.42.6. Review the linked Chromium report and Purr Data issue #572 before determining whether a compatible newer version exists; done means the chosen version works without the reported regressions.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.