Skip to content

fix: handle renderer startup load failures#51

Open
itzptk wants to merge 1 commit into
mainfrom
fix/issue-49-renderer-load-failures-20260606004855
Open

fix: handle renderer startup load failures#51
itzptk wants to merge 1 commit into
mainfrom
fix/issue-49-renderer-load-failures-20260606004855

Conversation

@itzptk

@itzptk itzptk commented Jun 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • route all main/tray renderer loads through a shared diagnostic loader that logs window, route, target URL/file, and serialized error before rethrowing
  • add top-level bootstrap failure logging so startup rejections no longer disappear as unhandled promises
  • keep window creation/lifecycle setup synchronous, register IPC before awaited startup renderer loads, and cover load-failure logging with Vitest

Verification

  • git diff --check
  • npm run test:node -- renderer-loader
  • npm run test:node
  • npm run test:all
  • npm run build
  • independent review: passed after follow-up fix

Manual invalid ELECTRON_START_URL app launch was attempted, but this Linux runner has no X server/display, so Electron exits before app code reaches renderer loading.

Closes #49

@itzptk itzptk force-pushed the fix/issue-49-renderer-load-failures-20260606004855 branch from 11e97c3 to fdea4f9 Compare June 5, 2026 23:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle renderer load failures during window startup

1 participant