Skip to content

//renderer:renderer_server_test fails when mozc_renderer is already running in Windows #1421

Closed

Description

@yukawa

Description

//renderer:renderer_server_test fails when mozc_renderer is already running in Windows.

Steps to reproduce

  1. Build Mozc64.msi and install it.
  2. Enable Mozc in some applications and make sure that Mozc's candidate window is shown.
  3. bazelisk test --config oss_windows -c dbg //renderer:renderer_server_test --nocache_test_results --test_output=streamed

Expected behavior

The test succeeds at the step 3.

Actual behavior

The test fails with the following error:

[ RUN      ] RendererServerTest.IPCTest
F1231 18:30:45.528271   18296 win32_ipc.cc:492] CreateNamedPipe failed231
*** Check failure stack trace: ***
    @   00007FF65B7D63F7  (unknown)
    @   00007FF65B7D6384  (unknown)
    @   00007FF65B725C58  (unknown)
    @   00007FF65B861FF3  (unknown)
    @   00007FF65B732B80  (unknown)
    @   00007FF65B7222C8  (unknown)
    @   00007FF65B722108  (unknown)
    @   00007FF65B721BDE  (unknown)
    @   00007FF65B7A8160  (unknown)
    @   00007FF65B7809F8  (unknown)
    @   00007FF65B7646A3  (unknown)
    @   00007FF65B7651E9  (unknown)
    @   00007FF65B765A8B  (unknown)
    @   00007FF65B77409D  (unknown)
    @   00007FF65B7A9490  (unknown)
    @   00007FF65B783B58  (unknown)
    @   00007FF65B773B01  (unknown)
    @   00007FF65BC9BE71  (unknown)
    @   00007FF65BC9BE42  (unknown)
    @   00007FF65BD23FF9  (unknown)
    @   00007FF65BD24132  (unknown)
    @   00007FF65BD241BE  (unknown)
    @   00007FF65BD241DE  (unknown)
    @   00007FF83D99E8D7  (unknown)
    @   00007FF83E48C53C  (unknown)

Version or commit-id

d91f278

Environment

  • OS: Windows 11 25H2

Activity

  1. nvssai11 commented on Jan 1, 2026

    @nvssai11

    @yukawa I’d like to help work on this issue and investigate the test failure when mozc_renderer is already running on Windows. Could you please assign it to me?

  2. yukawa commented on Jan 2, 2026

    @yukawa
    CollaboratorAuthor

    Hi @nvssai11,

    Thank you for your interest in contributing to this issue.

    While fixing this bug might seem straightforward, the solution involves a subtle trade-off regarding how much test-specific logic we should expose in the production code. Since this touches on the project's core design philosophy regarding testability, I believe it would be more efficient for the maintainers to discuss and implement the fix directly.

    I will assign this issue to myself and handle it. I appreciate your willingness to help!

  3. self-assigned this
    on Jan 2, 2026
  4. added a commit that references this issue on Jan 23, 2026
  5. added 3 commits that reference this issue on Jan 25, 2026
    ebfe437
    edbfddd
    1a6bbc9
  6. added a commit that references this issue on Mar 16, 2026
    1ca9b81
  7. added a commit that references this issue on Mar 27, 2026
    858f8c0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions