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

WASM Not Initialized in human #39

Closed
djthegr8 opened this issue Nov 25, 2020 · 5 comments
Closed

WASM Not Initialized in human #39

djthegr8 opened this issue Nov 25, 2020 · 5 comments
Assignees
Labels
question Further information is requested

Comments

@djthegr8
Copy link

Issue Description
Due to WASM not initialized and directly used, possible problem in the library.
WASM was not initialized, run tf.ready() or tf.setBackend("wasm") before doing this
Steps to Reproduce
Use the demo
Expected Behavior
No errors
Environment

  • Browser or NodeJS and version (e.g. NodeJS 14.15 or Chrome 86) Chrome
  • OS and Hardware platform (e.g. Windows 10, Ubuntu Linux on x64, Android 10) win10-x64
  • Packager (if any) (e.g, webpack, rollup, parcel, esbuild, etc.) -

Additional

  • For installation or startup issues include your package.json
  • For usage issues, it is recommended to post your code as gist
    N/A
@vladmandic
Copy link
Owner

are you running demo on your system or demo provided on github pages? i cannot reproduce using either.

if on your system, how did you deploy human?

this is most likely due to tfjs-backend-wasm-*.wasm file could not be loaded.
check in chrome or firefox inspector, network tab for any network requests for .wasm files:

  • what is the http status code for the request
  • what is the full path of the http request
  • do you have wasm files on your test system in that path?

@vladmandic vladmandic added the question Further information is requested label Nov 25, 2020
@djthegr8
Copy link
Author

djthegr8 commented Nov 25, 2020 via email

@vladmandic
Copy link
Owner

I cannot reproduce.

Please provide the info I've asked for and I'll investigate.
Also best to copy entire console output, not just one line.

@djthegr8
Copy link
Author

Can't reproduce anymore, will try to get the Laptop then reopen 👍

@vladmandic
Copy link
Owner

Possibly related to incompatibility with Chrome 87 that was just released and I fixed earlier today. I don't think it's strictly WASM related, but worth noticing.

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

No branches or pull requests

2 participants