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

[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

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

[nosachamos]

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

[vikramsamak]

is there any solution?? (tweaks)?

[emilioh93]

I have the same problem apparently

[nosachamos]

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]

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]

You bet, good luck!

[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

[guillaume-mueller]

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

[nosachamos]

@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]

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]

Ok, it worked for me but maybe you faced a different issue. Glad to hear you dont have this issue anymore.

…

On Sun, Dec 22, 2024, 8:05 AM Guillaume Müller ***@***.***> wrote: 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. — Reply to this email directly, view it on GitHub <#536 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJUA5R2HS3BMPONATVLAYL2G3BJTAVCNFSM6AAAAABUBNYZHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQ3DONRYGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>