Apologies for the quiet. So I don’t think there are any others, but this is really weird. There are no other directories, you’ve found all of them. The only one that matters is the one that goes by
Air Labs / Aether ... that is your profile. For the app to start multiple times, I would need to have something like either there are multiple binaries somewhere that is starting on the application boot, or the app spawns the multiple binaries on its own, thinking that it has crashed.
Could you answer these questions?
Q1: When you disable the start at boot, and restart your computer, does the multiple backends thing happen?
If yes, you have multiple records on your Start menu > Startup programs (I don’t know exactly what is called in Italian, but something similar)
- If no, and the multiple processes start when you only start Aether, that means the app is thinking that the backend or the frontend has crashed, and is spawning.
Q2: When you start the app, does the multiple processes start immediately, or 2nd, 3rd… etc processes come a while after? Especially when you are doing something like posting or upvoting.
If immediately, the app is thinking that the backend or frontend has crashed, and restarting it, and the backend/frontend becoming unresponsive happens right after launch.
If later, the backend/frontend does something that goes into the unresponsive state, and after a while the client decides that they are gone and ‘restarts’ them, and links itself to the newly spawned be/fe. The issue is, the old be/fe was busy, not crashed, and it comes back online after doing its job, to find out that it is now orphaned.
My suspicion is that, considering that you also have slowness problems, the frontend compilation thing (the part that you have slowness issues with) is taking so long on your computer that the client (the UI app) is deciding that the frontend hasn’t been responding for a long time, and it is probably dead. To be fair, this is not a bug, the client needs to be able to spawn a new frontend when the old one goes dead so as to not break the app and most of the time this happens it’s actually the right choice. In your case though, it’s the rare case where the frontend isn’t dead but actually doing work, but the client waits so long that it decides it is dead.
So my impression is that your two issues (speed and this multiplication) are actually the same issue, repsesenting itself in different ways. I’m currently working on an intermediate caching layer between disk and the app to be added to the app so that the app can use much less disk, and reduce reads and writes. I know that you use your computer for other things so maybe until I actually push the new version you might want to keep the app closed. I’m currently working on this, this is a fairly complex backend thing so I need to fully test that it actually compiles correctly. But I suspect when it comes it’s going to fix both of your problems. I’d expect, a few days, a week if everything goes right? I’m also having long compile times on my computer and I want to fix it, so I’m investigating a couple ways of improving this. No guarantees, but this is on top of my todo list and I’m currently actively working on this because it’s going to improve it for everybody.