Memory issues in browser

Memory issues in browser

  1. JavaScript does not allow forcibly releasing resources (memory). However, it is important to note that if a new scene is created when switching the model, then all objects in the old scene should be deleted using "scene.clear()".
  2. Most browsers have memory allocation limits for tabs (for example, 4GB per tab for Chrome, Edge).


    • Related Articles

    • What to do if there is not enough virtual memory?

      Large models can cause errors when there is not enough virtual memory allocated for the system to process big files successfully. Increasing virtual memory can be done as follows: Navigate to the **System** section of the Windows Control Panel: ...

    • Visualization requirements

      There are no explicit requirements for the graphical environment on the PC, because browser capabilities are used for rendering. But "hardware accelerated rendering" setting can affect performance.

    • How to import and visualize 2D drawings in Web Toolkit

      We have a ready-made Drawing Viewer Example that shows drawings: sheets, layers, elements in a browser. Its source code is available here on GitHub. It can be implemented into your solution. In order for the Web Toolkit to display the drawing, the ...

    • How to work with PMI (Product Manufacturing Information)?

      Work with PMI should be performed using ModelData_PMIData class. We have a number of examples demonstrating: - Traversal of PMI in a 3D model - Visualization of PMI from a 3D model - Working with PMI in Unity - Visualization of PMI in a web-browser ...

    • I'm writing a plugin for Siemens NX. CAD Exchanger SDK libraries won't load.

      Our CadExCore.dll library depends on another system library - dbgeng.dll. In turn, dbgeng.dll depends on another library - dbghelp.dll. Siemens NX loads and uses its own copy of dbghelp.dll instead of the system one. NX's version of this library is ...