MicrosoftEdge / MicrosoftEdge/WebView2Feedback

crash in EmbeddedBrowserWebView

Open
#5,614 2 comments 0 reactions 1 assignee View on GitHub

@ambikakunnath is already working on this.

Since Jun 24, 2026.

Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

My app use webview2, but crush on start. Only 1 user happened many times.
If need more info, please comment.

OSVersion
10.0.26200.8390

CpuInfo
Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz

GpuInfo
Intel(R) UHD Graphics; driver: 31.0.101.2135

SysInfo
AppCpuUsage
18.36%
AppMemoryPercent
2.47%
AppPrivateMemory
192MB
SystemCpuLoad
78.41%
SystemMemoryLoad
83%
SystemTotalPhysicalMemory
7824MB

EXCEPTION_ILLEGAL_INSTRUCTION / 0x7ffc606cefff: Fatal Error: EXCEPTION_ILLEGAL_INSTRUCTION / 0x7ffc606cefff
EmbeddedBrowserWebView0x7ffc606cefff ipcz::NodeLink::OnAcceptParcel
EmbeddedBrowserWebView0x7ffc606cff3f ipcz::msg::NodeMessageListener::OnTransportMessage
EmbeddedBrowserWebView0x7ffc606cc5ed ipcz::anonymous namespace'::NotifyTransport EmbeddedBrowserWebView0x7ffc606ca7ec mojo::core::ipcz_driver::Transport::OnChannelMessage EmbeddedBrowserWebView0x7ffc606c5a76 mojo::core::Channel::OnReadComplete EmbeddedBrowserWebView0x7ffc606cb0cc mojo::core::anonymous namespace'::ChannelWin::OnIOCompleted
EmbeddedBrowserWebView0x7ffc606e9a21 base::MessagePumpForIO::WaitForWork
EmbeddedBrowserWebView0x7ffc606e93e5 base::MessagePumpForIO::DoRunLoop
EmbeddedBrowserWebView0x7ffc6079701c base::MessagePumpWin::Run
EmbeddedBrowserWebView0x7ffc607b3767 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run
EmbeddedBrowserWebView0x7ffc607b9a15 base::RunLoop::Run
EmbeddedBrowserWebView0x7ffc607a2fe3 base::Thread::Run
EmbeddedBrowserWebView0x7ffc607a30fc base::Thread::ThreadMain
EmbeddedBrowserWebView0x7ffc60793ad2 base::`anonymous namespace'::ThreadFunc
KERNEL32.DLL 0x7ffcc92ee8d6 BaseThreadInitThunk
ntdll 0x7ffcca8cc3fb RtlUserThreadStart

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.