Skip to content
This repository was archived by the owner on Jun 22, 2025. It is now read-only.
This repository was archived by the owner on Jun 22, 2025. It is now read-only.

When overloaded with calls, Eel dies with "eel.js:115 WebSocket connection to '...' failed: Invalid frame header" #536

Open

Description

@nosachamos

Eel version
Eel 0.14.0

Describe the bug
I still have this issue. It happens when eel seems overloaded with messages.

eel.js:115 WebSocket connection to 'ws://localhost:8080/eel?page=index.html' failed: Invalid frame header

image

Not sure what to do with it right now as this is a total blocker, once it happens Eels just dies.

To Reproduce
I have a system in which thousands of calls are made from the Python code to JS code. After a few seconds of this, I get this issue. I don have a repro code that is standalone, but perhaps having method calls in loop would do it.

Expected behavior
Eel should not die, or should recover if this happens.

Desktop (please complete the following information):
Ubuntu, Chrome

Activity

  1. nosachamos commented on Oct 20, 2021

    @nosachamos
    Author

    I'm wondering if this could be caused by #540

  2. vikramsamak commented on Oct 22, 2022

    @vikramsamak

    is there any solution?? (tweaks)?

  3. emilioh93 commented on Dec 18, 2023

    @emilioh93

    I have the same problem apparently

  4. nosachamos commented on Dec 18, 2023

    @nosachamos
    Author

    I made a PR to fix this but it was never merged.

    #542

    There is a memory leak actually. This PR fixes it and I have a system running it with billions of calls done continuously and no issues.

    The project seems abandoned actually... I'm using my own fork with this fix instead. No more problems.

  5. emilioh93 commented on Dec 18, 2023

    @emilioh93

    It's great that you found a way to fix it. It really strikes me that it stopped working suddenly, but I will look into your solution to understand more about the origin of the problem. Thank you very much for answering my message @nosachamos

  6. nosachamos commented on Dec 18, 2023

    @nosachamos
    Author

    You bet, good luck!

  7. zhaoyuzhi983 commented on Mar 19, 2024

    @zhaoyuzhi983

    I'm also having this issue, but I don't have any issues when debugging in the IDE, the problem appears quickly after packaging, and as long as the eel is triggered frequently, I will have a similar problem

  8. guillaume-mueller commented on Dec 22, 2024

    @guillaume-mueller

    I have the same issue, tried the @nosachamos fix which didn't solved it. Damn.

  9. nosachamos commented on Dec 22, 2024

    @nosachamos
    Author

    @guillaume-mueller you need my PR

    #542

    This does solve the issue. I wish it had been merged but the project is dead it seems. I had to fork it to use this fix. Then the issue is gone

  10. guillaume-mueller commented on Dec 22, 2024

    @guillaume-mueller

    Your PR is what I was referring to by your "fix". It didn't work. Anyway I went for another way of transferring datas and I don't have the issue. But it is a bit concerning of an issue.

  11. nosachamos commented on Dec 22, 2024

    @nosachamos
    Author
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions