Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nw.js 114 error #7110

Closed
johnyc3 opened this issue Jun 12, 2023 · 4 comments
Closed

nw.js 114 error #7110

johnyc3 opened this issue Jun 12, 2023 · 4 comments
Assignees
Labels

Comments

@johnyc3
Copy link

johnyc3 commented Jun 12, 2023

Problem description

Building with newest nw.js 114 , the game does not load, and shows this error. (nothing to do with any addons)

Sprite-0001

Attach a .c3p

skymen's file below

Steps to reproduce

1.skymen's comment below

Observed result

The game loads black screen

Expected result

Works

More details

Affected browsers/platforms:

Chrome

First affected release:

344.2 Stable

System details

View details

PASTE HERE

@Laserwolve
Copy link

@johnyc3, this looks like an NW.js issue, with 0.76.1 and newer:
nwjs/nw.js#8075
https://github.com/Laserwolve-Games/DaggerQuest/issues/42
I don't think it's related to Mikal's plugin. DaggerQuest has no add-ons and experiences this issue. I was unable to create a minimal reproducible example so I refrained from filing a bug report.

It's most likely related to worker mode. Set Use worker to No as a temporary workaround.

@skymen
Copy link

skymen commented Jun 12, 2023

Did some testing, as mentionned in the github issue above and yep this isn't linked to Mikal's 3D Object addon
From my testing, this is only broken inside workers, not on the main thread

(Sorry, file too big for Github)

The bug still happens in 0.77.0 but started in 0.76.1 as mentionned in the issue mentionned by @Laserwolve

version 113 of C3's NW.js uses 0.76.0 and version 114 uses 0.77.0 which is why it's broken only on 114

EDIT: Source C3P for minimal repro:
createObjectUrl.zip

This is the one event:
image

And just for good measure:

Steps:

  • Enable Worker mode
  • Export
  • Run
  • Open dev tools

Observed result:
Error in console

The error doesn't happen with worker disabled.
I have only tested NW.js for Windows x64. It is possible this doesn't happen on other platforms.

@johnyc3
Copy link
Author

johnyc3 commented Jun 12, 2023

ok thanks guys. edited

@AshleyScirra AshleyScirra self-assigned this Jun 15, 2023
@AshleyScirra
Copy link
Member

This looks like this bug in NW.js so closing this issue as it will be followed-up there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants