Closed yaseenisolated closed 3 months ago
The backtrace isn't very useful. I should probably run it with debugging symbols?
thread 'tokio-runtime-worker' panicked at libs/user-facing-errors/src/quaint.rs:167:18:
internal error: entered unreachable code
stack backtrace:
0: 0x1177a0e9c - _napi_register_module_v1
1: 0x117095bb0 - <unknown>
2: 0x117784574 - _napi_register_module_v1
3: 0x1177a46c4 - _napi_register_module_v1
4: 0x1177a4014 - _napi_register_module_v1
5: 0x1177a4e7c - _napi_register_module_v1
6: 0x1177a49d0 - _napi_register_module_v1
7: 0x1177a4960 - _napi_register_module_v1
8: 0x1177a4954 - _napi_register_module_v1
9: 0x117ad6068 - _napi_register_module_v1
10: 0x117ad6190 - _napi_register_module_v1
11: 0x117828660 - _napi_register_module_v1
12: 0x117739ad8 - _napi_register_module_v1
13: 0x11775c260 - _napi_register_module_v1
14: 0x117769b70 - _napi_register_module_v1
15: 0x11757c0e8 - _napi_register_module_v1
16: 0x11759c818 - _napi_register_module_v1
17: 0x11759d128 - _napi_register_module_v1
18: 0x116faa6e8 - <unknown>
19: 0x116fac2b8 - <unknown>
20: 0x116fca13c - <unknown>
21: 0x116fc4f6c - <unknown>
22: 0x116fb3664 - <unknown>
23: 0x11701f14c - <unknown>
24: 0x116febae4 - <unknown>
25: 0x116ffc740 - <unknown>
26: 0x1177bb334 - _napi_register_module_v1
27: 0x1177c586c - _napi_register_module_v1
28: 0x1177b96c0 - _napi_register_module_v1
29: 0x1177b9140 - _napi_register_module_v1
30: 0x1177bf1a4 - _napi_register_module_v1
31: 0x1177a5db8 - _napi_register_module_v1
32: 0x183bc5034 - __pthread_joiner_wake
Ah. I had a mistake in my test harness. looks like this only consistently crashes around concurrency level 100.
Hey @yaseenisolated, thanks for reporting. Just to confirm, does the snippet you shared consistently reproduce the bug? Thank you!
Pretty consistently. I would say half the time if you set the concurrency to 100
Note that there might be related issues for SQLite under https://github.com/prisma/prisma/issues?q=is%3Aopen+label%3A%22topic%3A+Promise.all%22+sort%3Aupdated-desc
Hi @yaseenisolated, we believe we have a fix for this issue.
We plan on releasing it with the next stable version of Prisma (5.16.0
), but in the meantime, we'd like to collect some early feedback directly from the impacted users. Can you please try installing Prisma 5.16.0-integration-sqlite-fix.1
, and confirm that you can no longer experience this bug with it? Thanks!
pnpm install -D prisma@5.16.0-integration-sqlite-fix.1
pnpm install @prisma/client@5.16.0-integration-sqlite-fix.1
(Please note that this Prisma version is unstable, so we don't recommend running it in production.)
Hello! This issue was solved via https://github.com/prisma/prisma-engines/pull/4907. The fix is already available on Prisma 5.15.1.
Please make sure you update the prisma
CLI, the @prisma/client
library, and run prisma generate
again :)
Hi Prisma Team! My Prisma Client just crashed. This is the report:
The code shown below gets this crash pretty consistently with concurrency set to 100
Versions
I have also reproduced this on linux-x64
Logs
Code
Schema