pywalfox: Error: Native application tried to send a message of 1634038339 bytes, which exceeds the limit of 1048576 bytes

Overview

I’m getting this error in the debug output of the Firefox plug-in itself and a couple of related errors, but I think they are caused by the original error, but I’ll include them anyway. I have gone through the troubleshooting section in the README.md and everything there seems to be correct on my system.

Errors

  • Firefox plugin: Disconnected from native app: Error: Native application tried to send a message of 1634038339 bytes, which exceeds the limit of 1048576 bytes.
  • Firefox console: Error: Attempt to postMessage on disconnected port
  • pywalfox.py: Traceback (most recent call last): File "./pywalfox.py", line 21, in <module> client = uds.UDSClient() File "/mnt/data/Downloads/Pywalfox/daemon/uds.py", line 43, in __init__ self.s.connect(HOST) File "/usr/lib/python2.7/socket.py", line 228, in meth return getattr(self._sock,name)(*args) socket.error: [Errno 111] Connection refused
  • If run with python3: Traceback (most recent call last): File "pywalfox.py", line 21, in <module> client = uds.UDSClient() File "/mnt/data/Downloads/Pywalfox/daemon/uds.py", line 43, in __init__ self.s.connect(HOST) ConnectionRefusedError: [Errno 111] Connection refused

Specs

Firefox 74 OS: Pop!_OS 19.10 python --version: 2.7.17 python3 --version: 3.7.5

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 30 (15 by maintainers)

Commits related to this issue

Most upvoted comments

I believe I have fixed this issue. Apparently, the issue was a print() used for debugging when setting up the UNIX-socket server.

4 hours well spent…

Quick and dirty workaround if you have python3 on your machine: Change the shebang (first line of script Pywalfox/daemon/pywalfox.py) from #!/usr/bin/env python to #!/usr/bin/env python3

Oh almost forgot, thanks Frewacom for your great work and thanks for posting it on unixporn.

No problem. I am just glad I don’t have to debug another issue like this.

Odd, I changed back and now it runs like a charm. Changed nothing else. Sorry for the false alarm.

No need to apologize, I’m already happy that someone decided to make this. And besides, I have to stay at home anyway because of covid-19. Anyway, I tried it and unfortunately after a firefox restart the original error is back again. I’ll read myself a bit into that and see if I can figure something out