Skip to content

Fix misleading [BrowserMessage] log tag on generic source ops#1725

Open
summeroff wants to merge 1 commit into
stagingfrom
fix/misleading-browsermessage-log-tag
Open

Fix misleading [BrowserMessage] log tag on generic source ops#1725
summeroff wants to merge 1 commit into
stagingfrom
fix/misleading-browsermessage-log-tag

Conversation

@summeroff
Copy link
Copy Markdown
Contributor

What

Three OSN log lines were tagged [BrowserMessage] but actually log generic obs_source operations, not browser-specific ones:

  • osn::Source::Update (osn-source.cpp) — generic source settings update
  • osn::Source::SendMessage (osn-source.cpp) — calls generic obs_source_send_message
  • CallbackManager::GlobalQuery (callback-manager.cpp) — pumps obs_source_get_messages for all sources

This misdirects log/crash triage — e.g. a media-source settings update shows up as a [BrowserMessage].

Change

Retag those three logs [BrowserMessage] -> [osn-source]. String-literal text only: no logic, format specifiers, or behavior change. The genuinely browser-specific [BrowserMessage] logs in the obs-browser plugin are intentionally left untouched.

Testing

Log-string-only change; no functional impact. Not separately built locally (string-literal edit with identical %s/%llu specifiers and arg counts).

🤖 Generated with Claude Code

osn::Source::Update, osn::Source::SendMessage, and CallbackManager's
source-message pump are generic obs_source operations, not browser
specific. Retag their logs [BrowserMessage] -> [osn-source] so log
triage isn't misdirected. No behavior change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

1 participant