Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

GET RID OF WebView2!!

 I hate WebView2!  I can't get anything done anymore on Power BI.   It's nothing but crash after crash.  Here's 1 of the 100 logs I probably have.  Webview2 Process Failed. Out of Memory?  @support  

 

Feedback Type:
Frown (Error)

Error Message:
WebView2 Process Failed: CefLoadToReportDialog, Source:https://ms-pbi.pbi.microsoft.com/pbi/FloatingDialog/CefDialog/KoCefDialog.htm ExitCode:2 Reason:Unexpected ProcessFailedKind:BrowserProcessExited ProcessDescription:

Stack Trace:
Microsoft.PowerBI.Client.Windows.WebView2.WebView2ProcessCrashException
at Microsoft.PowerBI.Client.Windows.WebView2.WebView2BrowserWrapper.OnWebViewProcessFailed(Object sender, CoreWebView2ProcessFailedEventArgs args)

Stack Trace Message:
WebView2 Process Failed: CefLoadToReportDialog, Source:https://ms-pbi.pbi.microsoft.com/pbi/FloatingDialog/CefDialog/KoCefDialog.htm ExitCode:2 Reason:Unexpected ProcessFailedKind:BrowserProcessExited ProcessDescription:

Invocation Stack Trace:
at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.UI.Shared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace, String exceptionMessage)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.GetStackTraceInfo(Exception e)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.ReportException(IWindowHandle activeWindow, IUIHost uiHost, FeedbackPackageInfo feedbackPackageInfo, Exception e, Boolean useGDICapture)
at Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.<>c__DisplayClass14_0.<HandleException>b__0()
at Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.PowerBI.Client.Windows.Utilities.UIBlockingAwareExceptionHandler.HandleException(Exception e)
at Microsoft.PowerBI.Client.Windows.CefHtmlForm.Microsoft.PowerBI.Client.Windows.ICefBrowserHost.OnFatalError(Exception e, String knownErrorMessage, String knownErrorDetailsUrl)
at Microsoft.PowerBI.Client.Windows.WebView2.WebView2BrowserWrapper.OnWebViewProcessFailed(Object sender, CoreWebView2ProcessFailedEventArgs args)
at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at Microsoft.Mashup.Client.UI.Windows.DialogWindowBase.ShowModal(IWindowHandle windowHandle)
at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoLoadToReportDialog.TryShowDialog(Report report, IExceptionHandler exceptionHandler, IPowerBIWindowService windowService, IQueryServices queryServices, IDesktopModelingHost modelingHost, LocalizedString title, LoadToModelContext loadToModelContext)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoLoadToReportDialog.<>c__DisplayClass16_0.<TryShowDialogForQueries>b__0()
at Microsoft.PowerBI.Client.Windows.Report.<>c__DisplayClass64_0`1.<SynchronizeLooselyWithQueries>b__0()
at Microsoft.PowerBI.Client.Windows.Report.<SynchronizeLooselyWithQueriesAsync>d__65`1.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.PowerBI.Client.Windows.Report.SynchronizeLooselyWithQueriesAsync[T](Func`1 getTask)
at Microsoft.PowerBI.Client.Windows.Report.SynchronizeLooselyWithQueries[T](Func`1 action)
at Microsoft.PowerBI.Client.Windows.Services.WarningDetectionService.<DetectReportLoadWarning>b__41_1()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass4_1.<Main>b__2()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.Main(String[] args)


Browser Name:
CefLoadToReportDialog

Browser Source:
https://ms-pbi.pbi.microsoft.com/pbi/FloatingDialog/CefDialog/KoCefDialog.htm

Browser ExitCode:
2

Browser Crash Reason:
Unexpected

Browser Crash Kind:
BrowserProcessExited

Browser Process Description:


PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.102.845.0","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.WebView2.WebView2BrowserWrapper","Error":"Microsoft.PowerBI.Client.Windows.WebView2.WebView2ProcessCrashException - WebView2 Process Failed: CefLoadToReportDialog, Source:https://ms-pbi.pbi.microsoft.com/pbi/FloatingDialog/CefDialog/KoCefDialog.htm ExitCode:2 Reason:Unexpected ProcessFailedKind:BrowserProcessExited ProcessDescription:","MethodDef":"OnWebViewProcessFailed","ErrorOffset":"125"}

Snapshot Trace Logs:
C:\Users\wsbridwell\AppData\Local\Microsoft\Power BI Desktop\FrownSnapShot62c5386a-0a41-4942-aa33-7a7699688108.zip

Model Default Mode:
Import

Model Version:
PowerBI_V3

Performance Trace Logs:
C:\Users\wsbridwell\AppData\Local\Microsoft\Power BI Desktop\PerformanceTraces.zip

Enabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_qnaLiveConnect
PBI_dynamicParameters
PBI_enhancedTooltips
PBI_enableWebView2
PQ_WebView2Connector
PBI_mobileAuthoringFormattingUI
PBI_useModernFormatPane
PBI_sparklines

Disabled Preview Features:
PBI_SpanishLinguisticsEnabled
PBI_azureMapVisual
PBI_dataPointLassoSelect
PBI_compositeModelsOverAS
PBI_scorecardVisual

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

PowerBINonFatalError_ErrorDescription:
WebView2 Process Failed: CefLoadToReportDialog, Source:https://ms-pbi.pbi.microsoft.com/pbi/FloatingDialog/CefDialog/KoCefDialog.htm ExitCode:2 Reason:Unexpected ProcessFailedKind:BrowserProcessExited ProcessDescription:

PowerBIUserFeedbackServices_IsReported:
True

 

Status: Accepted

Similar issue has been submited internal(ICM: 291218800), would update here as soon as possible if there is any progress about it.

 

Currently WebView2 infrastructure is needed after Feb 2022 release, see: Reminder: WebView2 will be required for the next Power BI Desktop release 

 

If you do not want WebView2, you can try to use previous version of Power BI Desktop as the thread mentioned which is added in your post.

 

Best Regards,
Community Support Team _ Yingjie Li

Comments
v-yingjl
Community Support
Status changed to: Accepted

Similar issue has been submited internal(ICM: 291218800), would update here as soon as possible if there is any progress about it.

 

Currently WebView2 infrastructure is needed after Feb 2022 release, see: Reminder: WebView2 will be required for the next Power BI Desktop release 

 

If you do not want WebView2, you can try to use previous version of Power BI Desktop as the thread mentioned which is added in your post.

 

Best Regards,
Community Support Team _ Yingjie Li

Anonymous
Not applicable

Hello,

Are you still running into issues with WebView2? the out of memory issues was a bug in chromium (nothing we could do on our end) which should be fixed next week. If you are running into any other issues, we would love to work with you and get them resolved. Please reach out to us at pbidesktopwebview2issues@service.microsoft.com

wbridwell79
Frequent Visitor

@Anonymous  I haven't had any issues in about 2-3 weeks.  Fingers crossed it continues.  Thank you for the follow up!

Element115
Power Participant

@v-yingjl @rahul @Anonymous guys, seriously!  Look at Edge WebView crapping out on this screenshot.  it can't handle more than 5GB on a 64GB machine with >50GB available!  How on Earth are we to test different smallish big data scenarios locally with PBI Desktop to see what works and what doesn't?  Not saying it has to be like this in the Service, but locally if you have the RAM available, then WebView shouldn't become the stumbling block!  

 

Please fix it.

 

webview2_process_failed_Screenshot 2022-05-11 141911.png