qu1ck

@lucasfernog are you sure this is not like #852 ? When looking at dangling references to leaked http response objects it looked like they were from some closures originating in...

@lucasfernog I tried your suggestion in https://github.com/tauri-apps/tauri/issues/3921#issuecomment-1115089647 to use http server as bypass invoke system. It does NOT help, memory for http response objects is still leaking. If I understand...

Ok, I'm fairly certain now that I have proof of memory leak in tauri code, not webview. I modified the repro I linked in comment above. Now it has 2...

Does `tauri-invoke-http`-like system also use `eval` somewhere? Because if not then we are dealing with 2 memory leaks.

> tauri-invoke-http doesn't use eval - it uses a localhost server. And it leaks memory. So, like I said, 2 independent memory leaks. See my last attachment in https://github.com/tauri-apps/tauri/issues/4026#issuecomment-1130633129

@ahkohd your invoke implementation does not help.  Lucas is claiming that it's yet another issue not related to eval leak. It's not obvious to me how c++/rust land streams...

I started working on this feature and have a dev build ready https://github.com/qu1ck/transgui/releases/tag/label-dev  You need server support too, repo here: https://github.com/qu1ck/transmission/tree/labels

Currently editing the labels is done via simple text field. I'd like to improve it with autocomplete and better UI. But maybe it can be done as a later step.

If labels are greyed out that means the server does not support labels. You need to upgrade to dev build of transmission server as well. When I make a pull...

My code has been merged. I don't know if I'll have time to improve the UI but it's usable now.