Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
The Power BI Desktop application is automatically closing the moment i open pbix file, but when i open a new file through windhows search it's opening.
I have updated the Power BI desktop application to new version.
I am getting frequently memory allocation error. My pbix file size is around 400MB.
I am gettign the below error some times.
Feedback Type:
Frown (Error)
Timestamp:
2024-11-26T10:44:09.5203868Z
Local Time:
2024-11-26T16:14:09.5203868+05:30
Session ID:
40827939-41a1-4f51-82ca-7958122d7d9d
Release:
November 2024
Product Version:
2.138.1004.0 (24.11) (x64)
Error Message:
Object reference not set to an instance of an object.
Stack Trace:
System.NullReferenceException
at Microsoft.PowerBI.Client.Windows.Services.AutoRecoveryManager.<>c__DisplayClass97_0.<<PerformAutoSave>b__1>d.MoveNext()
Stack Trace Message:
Object reference not set to an instance of an object.
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.Host.Document.SynchronizationContextExtensions.<>c__DisplayClass2_0.<SendAndMarshalExceptions>b__0(Object null)
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.Windows.DialogWindowBase.ShowModal(IWindowHandle windowHandle)
at Microsoft.Mashup.Client.UI.Shared.WebDialogs.WebDialog.<>n__0(IWindowHandle owner)
at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)
at Microsoft.Mashup.Client.UI.Shared.Ux.WindowService.ShowDialog[T](IDialog`1 dialog)
at Microsoft.PowerBI.Client.Windows.Services.PowerBIWindowService.Trace[T](String action, String title, String details, Func`1 showDialog, Func`2 getResult)
at Microsoft.PowerBI.Client.Windows.Services.PowerBIWindowService.Trace[T](String action, String title, String details, Func`1 showDialog)
at Microsoft.PowerBI.Client.Windows.Services.PowerBIWindowService.Microsoft.Mashup.Client.UI.Shared.Ux.IWindowService.ShowDialog[T](IDialog`1 dialog)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.GetApprovedFeedbackValues(IUIHost uiHost, IWindowService windowService, IWindowHandle screenshotWindow, IFeedbackInfo info)
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.PowerBIUnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.RunApplicationLegacy(String[] args)
at Microsoft.PowerBI.Client.Program.Main(String[] args)
PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.138.1004.0","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.Services.AutoRecoveryManager+<>c__DisplayClass97_0+<<PerformAutoSave>b__1>d","Error":"System.NullReferenceException","MethodDef":"MoveNext","ErrorOffset":"56","ErrorCode":""}
OS Version:
Microsoft Windows NT 10.0.22631.0 (x64 en-US)
CLR Version:
4.8 or later [Release Number = 533320]
Peak Virtual Memory:
70.7 GB
Private Memory:
762 MB
Peak Working Set:
0.99 GB
IE Version:
11.1.22621.0
User ID:
a7b71dff-fa54-4f33-8401-12698f2901c8
Telemetry Enabled:
True
PowerBIUserFeedbackServices_IsReported:
True
DPI Scale:
150%
Supported Services:
Power BI
Hi @Raghu2117 - It is likely due to a combination of large file size, resource constraints, and possible corruption or compatibility issues with the PBIX file.
Try opening Power BI Desktop in Safe Mode to prevent auto-recovery issues. Open a new file and disable Auto Recovery in Options > Global Options
Ensure your system has sufficient memory (16 GB or more) and storage space. Monitor usage via Task Manager when opening the PBIX file. As the file is large file sizes (e.g., 400 MB) can strain memory. Check for optimizations:
Remove unused columns and tables.
Use summarized or aggregated data.
Optimize DAX calculations and reduce the use of calculated columns.
Enable Large File Support:
If the data model uses large datasets, enable Large Dataset Storage Format under File > Options > Current File > Data Load.
Increase Memory Limit:
Adjust Power BI’s memory settings in Options > Global Options > Data Load > Power BI Desktop > Memory.
check on the above steps and i hope it helps.
What's new in the latest Power BI update - Power BI | Microsoft Learn
Proud to be a Super User! | |
Check out the July 2025 Power BI update to learn about new features.
User | Count |
---|---|
73 | |
71 | |
38 | |
28 | |
26 |
User | Count |
---|---|
99 | |
88 | |
62 | |
42 | |
39 |