I am running an E2E test, when I submit a form, a POST request is triggered by SUT. This request is taking more than 10 mins and then either crashed the Cypress runner or shows the result. When tested manually, the request returns the response within few seconds. This is the error that I am getting: We detected that the Chromium Renderer process just crashed. This is the equivalent to seeing the 'sad face' when Chrome dies. This can happen for a number of different reasons: - You wrote an endless loop and you must fix your own code - You are running Docker (there is an easy fix for this: see link below) - You are running lots of tests on a memory intense application. - Try enabling experimentalMemoryManagement in your config file. - Try lowering numTestsKeptInMemory in your config file. - You are running in a memory starved VM environment. - Try enabling experimentalMemoryManagement in your config file. - Try lowering numTestsKeptInMemory in your config file. - There are problems with your GPU / GPU drivers - There are browser bugs in Chromium You can learn more including how to fix Docker here: https://on.cypress.io/renderer-process-crashed I am using Cypress 12.10.0 and I have tried clearing the cache. Any help will be greatly appreciated

Hi! This is difficult to speculate about so I’m not sure what to suggest. Is it possible to share a reproduction? I guess one question I have is, what happens if you intercept the POST request and stub the response? It’s just a guess to rule out something related to the server. Does the request itself seem to work normally and Cy hangs after, or does it seem like the request never resolved?

@wide-eye-45012 You may try using other browsers. I have also faced similar issue while uploading a large file that is of 1 GB using the select file command. Then I tried the same code on the Firefox browser and the operation was completed. You may try the same because even I am searching for the solution