Skip to content

fix: crash in postMessageHandler on message without source - #172

Merged
cdamus merged 1 commit into
sokatoafrom
issues/4882
Jun 11, 2026
Merged

cdamus merged 1 commit into
sokatoafrom
issues/4882

Conversation

@cdamus

@cdamus cdamus commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Gracefully handle the case where the incoming message source is null.

For android-graphics/sokatoa#4882

Gracefully handle the case where the incoming message source is null.

For sarc-acl/sokatoa-internal#4882

Signed-off-by: Christian W. Damus <cdamus@eclipsesource.com>

@colin-grant-work colin-grant-work left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fix looks correct; I'm curious if we know why the sourceless message is being sent, but only under specific conditions?

@cdamus

cdamus commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator Author

The fix looks correct; I'm curious if we know why the sourceless message is being sent, but only under specific conditions?

I don't know what this message is. According to my research the most likely origin of such a message is something internal to the browser, not a "normal" message sent by the application or in response to any user action. I suspect that it's something specific to the Linux implementation of Chromium or Electron as I am unable to reproduce the message on Mac, not even with the packaged Electron app bundle and trying to launch second instances.

@cdamus
cdamus merged commit bad7380 into sokatoa Jun 11, 2026
1 check passed
@cdamus
cdamus deleted the issues/4882 branch June 11, 2026 21:46
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.

3 participants