donut-proxy remains in memory after application and browsers all closed down

[amd1890]

What happened?

Linux, 0.27.0

donut-proxy remains in memory after browser and application are closed

Steps to reproduce

open donut browser,
use wayfern based profile
close profile
close app completely
donut-proxy remains in memory and needs to be manually killed

Operating System

Linux

Donut Browser version

0.27.0

Which browser is affected?

Wayfern

Error logs or screenshots

No response

[zhom]

Hi there and thanks for the report! Is it in memory permanently?

There is a grace period in case the browser is restarted during use, such after disabling history in Camoufox. It might be removed when Camoufox is fully deprecated.

[amd1890]

Hi there and thanks for the report! Is it in memory permanently?

There is a grace period in case the browser is restarted during use, such after disabling history in Camoufox. It might be removed when Camoufox is fully deprecated.

I don't know if it's permanent, but it's for a long time, over 20 minutes?, and it also continues to write to the disk while not in use, which is concerning, as shown in system monitor, alternating between 1.3-2.7 KiB/s on a regular basis.

[zhom]

Can you please share the logs? Dead proxy process should be removed in 2 minutes after closing Wayfern

[amd1890]

Can you please share the logs? Dead proxy process should be removed in 2 minutes after closing Wayfern

How do you want me to log this or how do I log this? I can do it if you tell me the terminal command.

[khoazero123]

Mine is the same. donut-proxy.exe continues to run after exiting Donut.exe.

[amd1890]

Can you please share the logs? Dead proxy process should be removed in 2 minutes after closing Wayfern

I don't know how to log this. I can use the terminal. Do I just start it from the terminal and it will show what is wrong? Do I need to add --verbose? I am still learning about the computers.

[zhom]

Hi there and sorry for taking forever to get back to you! When I ask for logs, I always ask for the app logs as it is managing the lifetime of the proxy process. The logs for donut-proxy are stored at $TMP/donut-proxy-<config id>.log if you are curious.

In any case, I was able to reproduce and fix the issue in 0.27.1. I've been testing it for the past 2 weeks and can confirm that there are no zombie processes left when a browser process is killed on all operating systems. Thank you for the report!

[amd1890]

I just upgraded, have version .28.1 and donut-proxy is still there, also doing disk writes long after the program closes, which is concerning behavior.

A module loaded in memory continuing to write after program close is not expected behavior.

I also sometimes close the program very quickly, possibly before a browser profile is unloaded. This should not be closed. Latest Wayfern, latest donut, still a problem.

[amd1890]

@zhom please reopen this.

[zhom]

Sorry to hear that, @amd1890 . I'm no longer able to reproduce this. If you have restarted your device in the past 2 weeks, I would not expect to see any orphan processes. Can you please share the logs from the app here or via the email, contact@donutbrowser.com? Thanks in advance!

[amd1890]

Sorry to hear that, @amd1890 . I'm no longer able to reproduce this. If you have restarted your device in the past 2 weeks, I would not expect to see any orphan processes. Can you please share the logs from the app here or via the email, contact@donutbrowser.com? Thanks in advance!

I am not a professional developer. I can provide logs, but must know what to type into the bash terminal. I can cut and paste anything but need specific guidance. Importantly, I do not know if running donut in a terminal will even show logs for a sub-process that continues to reside in memory and make disk writes after closing because this is such abnormal behavior for an application.

This continues to happen every time I use the application and I manually shut down the process by killing it.