Excel does not crash if I open multiple blank books at once.I get the same crash whether I use the async officeruntime storage or the sync window storage.Browser (if using Office on the web): NAĪctually, this could very well be a document loading problem rather than a local storage issue.Operating System: Windows 10 Version 1909 Build 18363.1256.Office version number: Excel version 2011 Build 13426.20404.This is serious embarrassing bug which prevents users from opening multiple workbooks at once when add-in installed. Check your event log for the exception shown above. sideload the add-in by running from Visual Code Terminal -> Run Task -> Debug:DesktopĮxcel will crash.do npm install to get all required node modules then build it in Visual Code.Also attched are two simple workbooks wrkbk1.xlsx and wrkbk2.xlsx. I have attached a working project with one simple custom function which uses localStorage. This bug only happens on Windows Platform. It should not delete any stored items in localStorage after crash. I have created a simple test below which produces the bug consistently Expected BehaviorĮxcel should not crash when multiple instances are opened. The stored content in localStorage are also deleted after the crash If you open a second workbook in new instance of Excel, it will crash immediately and log the following error to the event log:įaulting application name: EXCEL.EXE, version: 6.20404, time stamp: 0x5fdea626įaulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5fd1d17dįaulting application start time: 0x01d6deb16973c7c1įaulting application path: C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXEįaulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll Using window.localStorage in a custom function in shared runtime seems to work as long as you have a single instance of Excel and one workbook open.
0 kommentar(er)
