Do you have an issue with a specific file(s)? yes .xlsx file
Can you reproduce using one of our samples or online demos? No
Are you using the WebViewer server? No
Does the issue only happen on certain browsers? No ( have tried on chrome as well as on mozilla )
Is your issue related to a front-end framework? Not sure
Is your issue related to annotations? No
Please give a brief summary of your issue:
(Think of this as an email subject)
So, I am using webviewer version 10.11.1 for my angular v17 project, lately faced an issue where i am trying to preview this .xlsx file containing 18k rows and 8 columns and file is around 5Mb large. Once the document starts loading on the webviewer everything seems perfectly fine but after some time the browser starts to slow down and eventually either user won’t be able to perform any action or the following attached image is shown to the user.
Please provide a link to a minimal sample where the issue is reproducible:
won’t be able to share due to security reasons, and also unable to replicate on the apryse demo page as well.
Hello, I’m AiRon, an automated tech support bot While you wait for one of our customer support representatives, I can help you with your question.
You’re experiencing performance issues when loading large .xlsx files in WebViewer, which can be a common challenge due to the size and complexity of the data being processed.
Some things you can try:
Consider using the preloadWorker option to load necessary resources upfront, which can help in managing large files more efficiently.
Optimize the WebViewer library by excluding unnecessary features or worker files that you don’t need. This can help reduce the load on the browser.
Investigate the option of using WebViewer Server for server-side rendering, which can offload processing from the browser.
Ensure that your application is running in a production environment with optimizations enabled, which can improve performance.
Monitor memory usage and browser performance using developer tools to identify any specific bottlenecks or memory leaks.
For heavy documents, I would consider using WebViewer Server that can offload client-side work which may be affecting your browser performance. I tested with a sample server and saw no performance drop:
But seems like we are not using Webviewer Server and are not planning to switch to that, so is there any alternative solution you can show for the webviewer client?
If the conversion is affecting performance, you can load the document directly (as a non-PDF) by forcing the file type. For example, setting loadAsPDF: false.
Alternatively, you can have a separate officeToPDF conversion function before loading the document into the Viewer and then loading the PDF version thereafter.
