CorePackages errors stack trace malformed thus making it stand out as separate error

EtNowis · March 10, 2025, 3:42am

We can see for example that Error: invalid argument #3 to 'format' (string expected, got nil) has no stack trace, but there is another separated error CorePackages ... invalid argument #3 to ... is recorded which clogging up the report.
It basically happened to all CorePackages related errors. We know the stack trace is malformed because when we copy it into forum, each line is only separated by a ‘space’, like so:

CorePackages.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:235: ------ Error caught by React ------ invalid argument #3 to 'format' (string expected, got nil) ------ Error caught by React ------ CorePackages.Workspace.Packages._Workspace.CapturesInExperience.CapturesInExperience.Utils.getCaptureStorageUsage:18 function formatBytes CorePackages.Workspace.Packages._Workspace.CapturesInExperience.CapturesInExperience.Utils.getCaptureStorageUsage:35 function getCaptureStorageUsage CorePackages.Workspace.Packages._Workspace.CapturesInExperience.CapturesInExperience.Components.CapturesGallery.GalleryActionContainer:82 CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberHooks.new:1536 function mountMemo CorePackages.Packages._Index.React.React.ReactHooks:176 function useMemo CorePackages.Workspace.Packages._Workspace.CapturesInExperience.CapturesInExperience.Components.CapturesGallery.GalleryActionContainer:81 CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberHooks.new:3124 function renderWithHooks CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberBeginWork.new:207 function renderWithHooks CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberBeginWork.new:1575 function mountIndeterminateComponent CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberBeginWork.new:3483 function beginWork CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:248 CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:1968 CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:1853 CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:1802 CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:934 CorePackages.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:961 CorePackages.Packages._Index.Scheduler.Scheduler.Scheduler:305 CorePackages.Packages._Index.Scheduler.Scheduler.Scheduler:261 CorePackages.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:183 function doWork CorePackages.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:219 function performWorkUntilDeadline

Expected behavior

Restore the correct format of the stack trace, so they appear correctly under the error, and not clogging up the error report

Page URL: https://create.roblox.com/dashboard/creations/experiences/6909379980/analytics/errors?rangeType=Last1Day&minTime=1740528000000&maxTime=1741349150664&tab=Analytics&filter_Text=invalid+argument

neonpair · March 10, 2025, 5:48pm

Hi, thanks for reporting this!

There are a couple issues going on here:

For this kind of stack trace we weren’t properly populating our creator analytics error log – this should be fixed soon for future errors.
The actual cause of these specific errors looks like it’s in Roblox code rather than your place code, and the issue causing those failures is now being investigated as well, it looks like there may be a fix on the way for those as well.

Hope these will help your future error reports to clear up soon!

friedrich1717 · March 11, 2025, 6:35pm

Hi:
The bug should have get fixed. Unfortunately we cannot change the existing log we stored.
But all following logs should have the actual stacktrace correctly populated to the stacktrace field.