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 }}
Repository navigation
Session terminates when REPL input touches any Java if connected to server with -H option #3806
CLI prints "Connection terminated", the Python API call raises "frida.TransportError: the connection is closed", and the session detaches with reason "connection-terminated".
Environment
Frida: 17.24.3, frida-tools 14.10.4.
Frida client running on either Android 17 emulator or on a Linux aarch64 host machine.
Frida server running on Android 17 emulator.
Potential cause/fix
When the REPL touches Java, frida-tools reads the java.js bridge file from disk (237 kb) and sends it to the server as a single message. That's what appears to exceed the limit.
This 128 kb limit appeared in libsoup 3.7.1 (looks like 17.24.x brings us up 3.8.0). SoupServer sets the limit for any connection created by add_websocket_handler (explains why only affects message to the server and not from). Looks like Frida already raised the default frame limit here, but there's now also a total message limit to override.
Anyway this change worked for me (I used 0 to disable the limit all together, just to validate. There's probably a better value to choose.):
In lib/base/socket.vala, in WebConnection's construct:
changed the title [-]Session terminates with a -H server connection when any Java called in REPL[/-][+]Session terminates when REPL input touches any Java if connected to server with -H option[/+]on Oct 19, 2026
Activity
[-]Session terminates with a -H server connection when any Java called in REPL[/-][+]Session terminates when REPL input touches any Java if connected to server with -H option[/+]AstralKitsune commentedon Oct 20, 2026
This is fixed in frida/frida-core@418f472
rdtmaster commentedon Oct 20, 2026
How to obtain a patched frida-gadget that addresses the issue?