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

Easily produced 'Worker Crash' with many simple concurrent http requests #791

Open
lemire opened this issue Apr 7, 2024 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@lemire
Copy link

lemire commented Apr 7, 2024

It is fairly easy to get 'Worker Crash' by stressing the server with, say, 10,000 simultaneous requests. The exact error is:

[Error ]: Worker Crash: An uncaught exception occured: remote endpoint: Transport endpoint is not connected

I have a simple demonstration.

Use a simpler server:

#include "crow.h"
int main() {
  crow::SimpleApp app;
  app.loglevel(crow::LogLevel::Warning);
  CROW_ROUTE(app, "/simple")([](){
    return "Hello world";
  });
  app.port(18080).multithreaded().run();
}

Then just issue a massive number of requests...

bombardier -c 10000 http://localhost:18080/simple

I am not getting similar failures with all other frameworks on the same system.

I am not claiming that it is a bug. This might very well be the desired/expected result as I am definitively stressing the server... and it is fine to have failed requests when under stress.

Feel free to close this issue if you think that there is no concern.

This might be related to #549

@gittiver gittiver added the bug Something isn't working label Apr 7, 2024
@gittiver gittiver self-assigned this May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants