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

Prisma studio fails with 'Fatal Error' message #851

Closed
ACregan opened this issue Feb 8, 2022 · 2 comments
Closed

Prisma studio fails with 'Fatal Error' message #851

ACregan opened this issue Feb 8, 2022 · 2 comments

Comments

@ACregan
Copy link

ACregan commented Feb 8, 2022

  1. Prisma version (prisma -v or npx prisma -v):
prisma                  : 3.10.0-dev.20
@prisma/client          : 3.10.0-dev.20
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 60b16207c02de858be08e861ddaf1739c77eb43e (at node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Migration Engine        : migration-engine-cli 60b16207c02de858be08e861ddaf1739c77eb43e (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine    : introspection-core 60b16207c02de858be08e861ddaf1739c77eb43e (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary           : prisma-fmt 60b16207c02de858be08e861ddaf1739c77eb43e (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Default Engines Hash    : 60b16207c02de858be08e861ddaf1739c77eb43e
Studio                  : 0.458.0
  1. Logs from Developer Tools Console or Command line, if any:

CONSOLE LOG:

[BootstrapStore.init] Studio bootstrap failed
{
  "message": "Invalid string length",
  "stack": "RangeError: Invalid string length\n    at JSON.stringify (<anonymous>)\n    at _t.serialize (http://localhost:5555/assets/index.js:1:49091)\n    at _t.update (http://localhost:5555/assets/index.js:1:12197)\n    at Cc (http://localhost:5555/assets/vendor.js:50:6994)\n    at _t.n (http://localhost:5555/assets/vendor.js:50:6688)\n    at _t.update (http://localhost:5555/assets/index.js:1:48948)\n    at Cc (http://localhost:5555/assets/vendor.js:50:6994)\n    at _t.n (http://localhost:5555/assets/vendor.js:50:6688)\n    at http://localhost:5555/assets/index.js:1:82151\n    at Array.forEach (<anonymous>)"
}

RangeError: Invalid string length
    at JSON.stringify (<anonymous>)
    at _t.serialize (:5555/assets/index.js:1:49091)
    at _t.update (:5555/assets/index.js:1:12197)
    at Cc (:5555/assets/vendor.js:50:6994)
    at _t.n (:5555/assets/vendor.js:50:6688)
    at _t.update (:5555/assets/index.js:1:48948)
    at Cc (:5555/assets/vendor.js:50:6994)
    at _t.n (:5555/assets/vendor.js:50:6688)
    at :5555/assets/index.js:1:82151
    at Array.forEach (<anonymous>)

STUDIO UI ERROR REPORT:

Invalid string length
RangeError: Invalid string length
    at JSON.stringify (<anonymous>)
    at _t.serialize (http://localhost:5555/assets/index.js:1:49091)
    at _t.update (http://localhost:5555/assets/index.js:1:12197)
    at Cc (http://localhost:5555/assets/vendor.js:50:6994)
    at _t.n (http://localhost:5555/assets/vendor.js:50:6688)
    at _t.update (http://localhost:5555/assets/index.js:1:48948)
    at Cc (http://localhost:5555/assets/vendor.js:50:6994)
    at _t.n (http://localhost:5555/assets/vendor.js:50:6688)
    at http://localhost:5555/assets/index.js:1:82151
    at Array.forEach (<anonymous>)
  1. Does the issue persist even after updating to the latest prisma CLI dev version? (npm i -D prisma@dev)
    Yes, I had this issue yesterday but upgrading to dev release stream it seemed to resolve it. However starting up my project again today, the error reoccurred, I tried upgrading again to latest DEV release but the problem persists.

  2. Prisma schema (if relevant):

Not applicable, the issue is that Prisma Studio fails to start.
@ACregan
Copy link
Author

ACregan commented Feb 8, 2022

WORTH NOTING FOR OTHER USERS (I see a lot of similar tickets):

Going to Application Tab, Clearing IndexedDB and Session In Application Tab in Chrome Dev Tools seems to have worked around the issue.

@janpio
Copy link
Contributor

janpio commented Apr 14, 2022

See #895

@janpio janpio closed this as completed Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants