Crash on Dumping Ram

[Bappsack]

On Large Games (ex. SwSh) it results almost anytime in a Connection Exception crash when u search & compare the current dump for a value, also sometimes on the first dump aswell.

Related function:

Noexes/client/src/me/mdbell/noexs/core/Debugger.java

Lines 259 to 285 in 8e8a75d

	public void readmem(long start, int size, OutputStream to) throws IOException {
	acquire();
	try {
	conn.writeCommand(COMMAND_READ);
	conn.writeLong(start);
	conn.writeInt(size);
	conn.flush();
	Result rc = conn.readResult();
	if (rc.succeeded()) {
	byte[] buffer = new byte[2048 * 4];
	while (size > 0) {
	rc = conn.readResult();
	if (rc.failed()) {
	conn.readResult();
	throw new ConnectionException(rc);
	}
	int len = readCompressed(buffer);
	to.write(buffer, 0, len);
	size -= len;
	}
	}
	conn.readResult();
	} finally {
	release();
	}
	}

Triggered Exception:

Noexes/client/src/me/mdbell/noexs/core/Debugger.java

Lines 272 to 275 in 8e8a75d

	if (rc.failed()) {
	conn.readResult();
	throw new ConnectionException(rc);
	}

[mdbell]

Could you provide the generated stack trace? It should contain an error code that would help with debugging your issue.

[Bappsack]

ConnectionException

Result[mod=1, desc=106}

The exception stacktrace was:

me.mdbell.noexs.core.ConnectionException: Result{mod=1, desc=106}
at me.mdbell.noexs.core.Debugger.readmem(Debugger.java:274)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:373)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.refineSearch(MemorySearchService.java:211)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:187)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:172)
at javafx.concurrent.Task$TaskCallable.call(Task.java:1425)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at javafx.concurrent.Service.lambda$executeTask$6(Service.java:725)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:391)
at javafx.concurrent.Service.lambda$executeTask$7(Service.java:724)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:832)

[mdbell]

The game is deallocating memory between dumps, there is already an issue for it (#17 to be exact). I'm going to close this issue as it it a duplicate.