Duplicates
Latest version
Current behavior 😯
When running AWS serverless, sometimes we get unexpected responses from server functions like:
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied</Message></Error>
This response causes an infinite loop which freezes the browser and causes a memory leak.
The response is handled in this function:
|
async function fetchServerFunction( |
|
result = await deserializeStream(instance, response); |
The infinite loop in:
The error:
|
const bytes = Number.parseInt(head, 16); // ;0x00000000; |
head = "?xml versi"
bytes = NaN
I can add a check for NaN but I think it might be worth to also handle unexpected responses higher up in the fetchServerFunction
Expected behavior 🤔
No response
Steps to reproduce 🕹
Steps:
Context 🔦
No response
Your environment 🌎
Duplicates
Latest version
Current behavior 😯
When running AWS serverless, sometimes we get unexpected responses from server functions like:
This response causes an infinite loop which freezes the browser and causes a memory leak.
The response is handled in this function:
solid-start/packages/start/src/runtime/server-runtime.ts
Line 143 in f4052b2
solid-start/packages/start/src/runtime/server-runtime.ts
Line 187 in f4052b2
The infinite loop in:
solid-start/packages/start/src/runtime/server-runtime.ts
Line 83 in f4052b2
The error:
solid-start/packages/start/src/runtime/server-runtime.ts
Line 60 in f4052b2
head = "?xml versi"
bytes = NaN
I can add a check for NaN but I think it might be worth to also handle unexpected responses higher up in the
fetchServerFunctionExpected behavior 🤔
No response
Steps to reproduce 🕹
Steps:
Context 🔦
No response
Your environment 🌎