chore: monitoring for bg-process

[Aarushsr12]

Summary by CodeRabbit

Bug Fixes

• Enhanced error handling for background process initialization with improved diagnostics and recovery
• Added runtime validation to detect and report background window unavailability issues
• Improved error tracking and logging for better stability and troubleshooting

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[linear]

ENGG-5202 FsAccessError: Level: Fatal Error invoking remote method 'forward-event-from-webapp-to-background-and-await-reply': TypeError: Object has been destroyed

[coderabbitai]

Walkthrough

This change introduces Sentry error reporting for background window lifecycle management in the main process. In setupIPCForwarding.js, runtime validation was added to check if the background window exists and is not destroyed on each IPC call, logging and reporting errors to Sentry when unavailable. In startBackgroundProcess.js, the background window creation is wrapped in a try/catch block with Sentry error reporting, and a closed event handler was added to detect and report unexpected window closures.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• fix: handle quit with proper cleanup #223 — Modifies src/main/actions/startBackgroundProcess.js to handle background-window lifecycle; this PR adds Sentry reporting and a closed-event handler while the related PR removes that handler.

Suggested reviewers

• nsrCodes
• RuntimeTerror10

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: monitoring for bg-process' directly corresponds to the main changes, which add Sentry monitoring and error handling for the background process with runtime validations.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

src/main/actions/setupIPCForwarding.js (1)

10-21: Stop forwarding when the background window is unavailable.

You report the error but still register a reply listener and call webContents.send, which will throw and leave a dangling ipcMain.once listener. Return early (resolve/reject) before installing the listener and sending.

🛠️ Proposed fix

-    async (event, incomingData) => {
-      return new Promise((resolve) => {
+    async (event, incomingData) => {
+      return new Promise((resolve, reject) => {
         // Check if backgroundWindow is available and not destroyed (check on each IPC call)
         if (!backgroundWindow || backgroundWindow.isDestroyed()) {
-          const errorMessage = "Background process unavailable during IPC communication";
-          console.error(errorMessage);
-          Sentry.captureException(new Error(errorMessage));
+          const error = new Error(
+            "Background process unavailable during IPC communication"
+          );
+          console.error(error.message);
+          Sentry.captureException(error);
+          return reject(error);
         }

src/main/actions/startBackgroundProcess.js (1)

3-52: Use the Electron main-process Sentry SDK here.

This runs in the main process; @sentry/browser is for renderer processes only and will not initialize properly here. The codebase already establishes the correct pattern—src/main/actions/setupIPCForwarding.js in the same directory uses @sentry/electron/main. Align with that pattern.

🛠️ Proposed fix

-import { captureException } from "@sentry/browser";
+import { captureException } from "@sentry/electron/main";

🤖 Fix all issues with AI agents

In `@src/main/actions/startBackgroundProcess.js`:
- Around line 85-88: The on("closed") handler for backgroundWindow currently
logs and captures the error but doesn't reset state; update that handler
(backgroundWindow.on("closed", ...)) to: clear global.backgroundWindow (set to
null), set any active flag such as isBackgroundProcessActive to false,
remove/clean any IPC listeners or references tied to backgroundWindow, and
ensure any local backgroundWindow variable is nulled so future
startBackgroundProcess()/restart logic can create a new window; include a brief
log entry indicating state was cleared after close.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Clear background window state on close to allow recovery.

The close handler reports the error but leaves global.backgroundWindow, state, and the active flag intact. That can block future restarts and keep IPC pointing at a destroyed window.

🛠️ Proposed fix

     backgroundWindow.on("closed", () => {
       console.error("Background window closed unexpectedly");
       captureException(new Error("Background window closed unexpectedly"));
+      global.isBackgroundProcessActive = false;
+      global.backgroundWindow = null;
+      void setState(null, { stateName: "backgroundWindow", newValue: null });
     })

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	backgroundWindow.on("closed", () => {
	console.error("Background window closed unexpectedly");
	captureException(new Error("Background window closed unexpectedly"));
	})
	backgroundWindow.on("closed", () => {
	console.error("Background window closed unexpectedly");
	captureException(new Error("Background window closed unexpectedly"));
	global.isBackgroundProcessActive = false;
	global.backgroundWindow = null;
	void setState(null, { stateName: "backgroundWindow", newValue: null });
	})

🤖 Prompt for AI Agents

In `@src/main/actions/startBackgroundProcess.js` around lines 85 - 88, The
on("closed") handler for backgroundWindow currently logs and captures the error
but doesn't reset state; update that handler (backgroundWindow.on("closed",
...)) to: clear global.backgroundWindow (set to null), set any active flag such
as isBackgroundProcessActive to false, remove/clean any IPC listeners or
references tied to backgroundWindow, and ensure any local backgroundWindow
variable is nulled so future startBackgroundProcess()/restart logic can create a
new window; include a brief log entry indicating state was cleared after close.