-
-
Notifications
You must be signed in to change notification settings - Fork 305
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
Comments
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 this is most likely due to
|
The Github Pages. I am able to do it well on my WebGL supported laptop,
however not on my WebGL unsupported one.
…On Wed, 25 Nov 2020 at 19:40, Vladimir Mandic ***@***.***> wrote:
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?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKQZA763FXC5JHR5TWBEB5TSRUF6JANCNFSM4UCL674Q>
.
--
*Thanks*
*Dweep*
|
I cannot reproduce. Please provide the info I've asked for and I'll investigate. |
Can't reproduce anymore, will try to get the Laptop then reopen 👍 |
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. |
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
Additional
package.json
N/A
The text was updated successfully, but these errors were encountered: