You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 22, 2025. It is now read-only.
Repository navigation
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
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
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
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
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
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.
Activity
nosachamos commentedon Oct 20, 2021
I'm wondering if this could be caused by #540
vikramsamak commentedon Oct 22, 2022
is there any solution?? (tweaks)?
emilioh93 commentedon Dec 18, 2023
I have the same problem apparently
nosachamos commentedon Dec 18, 2023
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.
emilioh93 commentedon Dec 18, 2023
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
nosachamos commentedon Dec 18, 2023
You bet, good luck!
zhaoyuzhi983 commentedon Mar 19, 2024
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
guillaume-mueller commentedon Dec 22, 2024
I have the same issue, tried the @nosachamos fix which didn't solved it. Damn.
nosachamos commentedon Dec 22, 2024
@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
guillaume-mueller commentedon Dec 22, 2024
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.
nosachamos commentedon Dec 22, 2024