You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
upgrade to tfjs4.3.0 from tfjs4.2.0 and immediately hit a regression issue.
tested in browser using webgl and in nodejs using tensorflow backends, both have same problem.
basically, some tensors are disposed immediately after model execution.
runtime error is obvious, but just to make it easily searchable by other users here's a stack trace:
node_modules/.pnpm/@[email protected]/node_modules/@tensorflow/tfjs-core/dist/tf-core.node.js:3882
throw new Error("Tensor is disposed.");
^
Error: Tensor is disposed.
at Tensor.throwIfDisposed (node_modules/.pnpm/@[email protected]/node_modules/@tensorflow/tfjs-core/dist/tf-core.node.js:3882:19)
at Tensor.<anonymous> (node_modules/.pnpm/@[email protected]/node_modules/@tensorflow/tfjs-core/dist/tf-core.node.js:3761:30)
at step (node_modules/.pnpm/@[email protected]/node_modules/@tensorflow/tfjs-core/dist/tf-core.node.js:140:27)
at Object.next (.pnpm/@[email protected]/node_modules/@tensorflow/tfjs-core/dist/tf-core.node.js:89:53)
at node_modules/.pnpm/@[email protected]/node_modules/@tensorflow/tfjs-core/dist/tf-core.node.js:82:71
at new Promise (<anonymous>)
at __awaiter (node_modules/.pnpm/@[email protected]/node_modules/@tensorflow/tfjs-core/dist/tf-core.node.js:68:12)
at Tensor.data (node_modules/.pnpm/@[email protected]/node_modules/@tensorflow/tfjs-core/dist/tf-core.node.js:3756:16)
The text was updated successfully, but these errors were encountered:
upgrade to
tfjs
4.3.0 fromtfjs
4.2.0 and immediately hit a regression issue.tested in browser using
webgl
and in nodejs usingtensorflow
backends, both have same problem.basically, some tensors are disposed immediately after model execution.
simple reproduction
result:
likely introduced via #7392 and attempted to fix via #7445 (but issue still exists)
also related issue #7431
i've tried a workaround by explicitly listing output tensors, but it does not help:
runtime error is obvious, but just to make it easily searchable by other users here's a stack trace:
The text was updated successfully, but these errors were encountered: