You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When we are exporting a notebook, the entire RAM of the system is used, causing the system to freeze and a need to forcefully shut down the system. The reason acc to me is that, when I see Task Manager, for every page exported, a Word program is spawned. So if there 1000 pages for eg, 1000 instances of word are opened. These are never killed. Even after the export is done, these programs remain.
Note: There are other programs running as well.
To Reproduce
Steps to reproduce the behavior.
Export a OneNote notebook.
Expected behavior
During the export of the notebook, I dont expect the entire system RAM to be consumed. And want to be working on other stuff while export is running
Logs
N/A
Desktop (please complete the following information):
OneNodeMdExporter version : 1.5.0
Windows version : Windows 10 22H2
Office Version : Microsoft 365 64 bit
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Describe the bug
When we are exporting a notebook, the entire RAM of the system is used, causing the system to freeze and a need to forcefully shut down the system. The reason acc to me is that, when I see Task Manager, for every page exported, a Word program is spawned. So if there 1000 pages for eg, 1000 instances of word are opened. These are never killed. Even after the export is done, these programs remain.
Note: There are other programs running as well.
To Reproduce
Steps to reproduce the behavior.
Export a OneNote notebook.
Expected behavior
During the export of the notebook, I dont expect the entire system RAM to be consumed. And want to be working on other stuff while export is running
Logs
N/A
Desktop (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: