BUG: Backend Serve and Sync Processes Keep Running After Closing PictoPy

[rahulharpal1603]

Discussed in #721

^{Originally posted by rohan-pandeyy December 12, 2025}
Hi @rahulharpal1603, I’m opening this discussion to confirm whether you agree with the points raised here, since this bug directly affects PictoPy’s production behavior. Once approved, this can be converted into an issue.

Current Behavior

I recently noticed, in the production build of PictoPy:

• When the app launches, the internal backend server and the sync process start automatically.
  

• But when the user closes PictoPy, both processes continue running in the background.
  

• These processes keep consuming memory/CPU even though the user believes the app has fully exited. (And the consumption only increases as more folders are added to the db)

I went through some other OS/Non OS applications, this shouldn't be an intentional background-service behavior.

[!IMPORTANT]
Closing the app = everything stops, there shouldn't be any hidden background daemons unless explicitly enabled...🤔

Even though I agree, having the server always running means the app opens and loads all images faster, if accidentally closed, or the user keeps opening and closing the app, but this should be a user choice whether they want "on clicking cross, shut down backend server and sync engine" or "keep the bg processes running".

What I'm proposing:

There should be an explicit user-facing toggle for "run in background" or "minimize to tray" along with a proper tray integration, in settings page, if you side with the "server always running means the app opens and loads all images faster" part...
Otherwise the background processes should automatically end in case you think a minimize to tray toggle is not required for PictoPy.

Kindly let me know if any other clarification from my side is required. :)

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[VasuS609]

Hey @rahulharpal1603, I’ve got a working fix for this—using Tauri to cleanly shut down the Python backend and sync processes when the app closes. Can I go ahead and submit a PR within the next 2 days?

[suhaib-ilahi]

Hey @VasuS609, this issue is already assigned to @rohan-pandeyy. You can help us test the new version before it's released; it will absolutely help a lot!

[rahulharpal1603]

@rohan-pandeyy, can you comment on this thread so that I can assign you this issue? Without your comment, GitHub won't allow me to assign.

[rohan-pandeyy]

@rahulharpal1603, Can you please assign me this issue?
Thanks :)

[rohan-pandeyy]

Hi @rahulharpal1603, the PR is ready but I require your guidance with a decision before opening. Could you please refer to this message and share me your views/ what step should I take or should I not worry about this for now at all?

Btw, working screen recording 👇

Graceful_Shutdown.mp4

[rahul-vyas-dev]

Hey @rohan-pandeyy , is this still available, or are you done with it?

[rohan-pandeyy]

Hey @rahul-vyas-dev, yes I'm done with the PR, just need to add some final touch ups to the PR