> Good news.
I'm here to report that, for the first time since I first give RB a trial in a couple of old Olk-Word integration Apps, with about 40 class-modules, and probably the same number of standard modules, I could be able to populate and see Code Inspections and Code Explorer. My office 365 installation is the same, only MS updated. And of course is the same machine.
Previously, for the last 2 y every time I tried RB, every time I had to kill VBE, Office and restart machine, sometimes co

> Good news.
I'm here to report that, for the first time since I first give RB a trial in a couple of old Olk-Word integration Apps, with about 40 class-modules, and probably the same number of standard modules, I could be able to populate and see Code Inspections and Code Explorer. My office 365 installation is the same, only MS updated. And of course is the same machine.
Previously, for the last 2 y every time I tried RB, every time I had to kill VBE, Office and restart machine, sometimes co

> Good news.
I'm here to report that, for the first time since I first give RB a trial in a couple of old Olk-Word integration Apps, with about 40 class-modules, and probably the same number of standard modules, I could be able to populate and see Code Inspections and Code Explorer. My office 365 installation is the same, only MS updated. And of course is the same machine.
Previously, for the last 2 y every time I tried RB, every time I had to kill VBE, Office and restart machine, sometimes co

> Hi @msdiniz,
if I didn't miss any relevant infos, you don't suffer on "Out of memory errors and excessively high memory usage" what this issue is about? Then please create a new issue and add log files. Some tipps for speedup:

- turn off all inspections you don't need
- don't use the bang(!)-operator (there are some new quick-fixes to remove them)
- shrink code size ;)

To be curious, what for do you need that amout of code for Word, Outlook?

> Hi @msdiniz,
if I didn't miss any relevant infos, you don't suffer on "Out of memory errors and excessively high memory usage" what this issue is about? Then please create a new issue and add log files.

Some tipps for speedup from the [blog](https://rubberduckvba.wordpress.com/2020/08/22/rubberduck-2-5-1/):

- Disable “run inspections automatically on successful parse”, so that they only run if you explicitly refresh them from the Inspection Results toolwindow;
- Set inspection severi

> Hi,

I'm not an expert on debug here, but as your issue is 5 days old, I'll try.

Exception is thrown by ExportAsSourceFile what exports your code to a textfile that is then pared (if I got that correct). As you use RDS I assume a problem with the path RD wants to store that files, but I have to look in code to see what path is used for that.. General advice is to always use the newest RD version, as they usually have lots of improvements. E.g. one new feature is version check on startup.