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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
smpa01
Super User
Super User

Maximum call stack size exceeded

I am getting the following error while I am trying to display a svg through a meaure.

Stack Trace Message:
An error occurred while rendering the report.

Detailed as following

 

Feedback Type:
Frown (Error)

Error Message:
An error occurred while rendering the report.

Stack Trace:
Javascript: Error
at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:3766:48
    at args.<computed> (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:112191:59)
    at ZoneDelegate.invokeTask (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:111075:193)
    at Object.onInvokeTask (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:78839:64)
    at ZoneDelegate.invokeTask (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:111075:76)
    at Zone.runTask (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:110957:67)
    at ZoneTask.invokeTask (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:111113:67)
    at ZoneTask.invoke (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:111107:60)
    at data.args.<computed> (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:112175:48)

Stack Trace Message:
An error occurred while rendering the report.

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.PowerBIUnexpectedExceptionHandler.HandleException(Exception e)
   at Microsoft.PowerBI.Client.Windows.Utilities.UIBlockingAwareExceptionHandler.HandleException(Exception e)
   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.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.PowerBI.Client.Windows.WebView2.WebView2Interop.InvokeCs(InteropCall call)
   at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
   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.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)


JS Error Message:
Maximum call stack size exceeded

RangeError: Maximum call stack size exceeded
    at RegExp.exec (<anonymous>)
    at TokenRuleSet.nextToken (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:198572:49)
    at tokenize (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:198796:46)
    at DaxParser.doParse (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:193265:59)
    at DaxParser.tryParse (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:193302:30)
    at parseExpressionChange (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:255667:53)
    at parseExpressionPosition (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:255661:24)
    at parseExpression (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:255658:24)
    at Function.DaxValidationProvider.triggerValidation (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:255734:48)
    at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js:255726:39

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.103.881.0","ModuleName":"https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.js","Component":"","Error":"Error","MethodDef":"","ErrorOffset":"3766:48"}

Snapshot Trace Logs:
C:\Users\smpa01\AppData\Local\Microsoft\Power BI Desktop\FrownSnapShot99fc781e-c941-42a0-96d8-088316cca034.zip

Model Default Mode:
Import

Model Version:
PowerBI_V3

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

Enabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_qnaLiveConnect
PBI_azureMapVisual
PBI_dataPointLassoSelect
PBI_compositeModelsOverAS
PBI_dynamicParameters
PBI_enhancedTooltips
PBI_enableWebView2
PQ_WebView2Connector
PBI_mobileAuthoringFormattingUI
PBI_useModernFormatPane
PBI_sparklines
PBI_scorecardVisual

Disabled Preview Features:
PBI_SpanishLinguisticsEnabled
PBI_lineChartError

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

PowerBIUserFeedbackServices_IsReported:
True

Formulas:


section Section1;

shared Table = let
    Source = Table.FromRows(Json.Document(Binary.Decompress(Binary.FromText("i45WMlSKjQUA", BinaryEncoding.Base64), Compression.Deflate)), let _t = ((type nullable text) meta [Serialized.Text = true]) in type table [Column1 = _t]),
    #"Changed Type" = Table.TransformColumnTypes(Source,{{"Column1", Int64.Type}})
in
    #"Changed Type";

Active Section Contract:
{"id":0,"name":"ReportSection","displayName":"Page 1","filters":"[]","ordinal":0,"visualContainers":[],"config":{},"displayOption":1,"width":1280,"height":720}

 

Does anyone know on top of their head what can cause this? My svg contains 2 path elements with each containing 360 d attributes. I am sorry I can't share this client-specific measure here.

@dm-p btw the same svg works without issues in browser and blazing fast.

 

I have also done any prior housekeeping before trying render it through a matrix, for example, converted to a data URI by prefixing

 

data&colon;image/svg+xml;utf8

and explicitly changed the type to image URL.

 

I just need to know what is the current limitation in terms of rendering svg (for example certain size, if I am utilizing a data driven path element it can become a path with many d attributes). If I know the limitation, I can generate my svg according to that.

 

Any pointers/suggestion/documentation would grately help. 

 

 

Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
My custom visualization projects
Plotting Live Sound: Viz1
Beautiful News:Viz1, Viz2, Viz3
Visual Capitalist: Working Hrs
1 REPLY 1
v-xiaotang
Community Support
Community Support

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.