I've also encountered a similar situation this week and I'm using Intella Professional 1.7.2-r26532. Processing gets to the recovery of deleted items and memory usage has stayed within 1GB of when I started the processing. Then, within a 5 second timeframe, memory usage consumes the maximum available (12GB on this PC), the disk activity light is solid and Windows appears to freeze. I think it is attempting to roll out chunks of memory to disk. I've narrowed it down to a single .OST file (1.1GB). I initially suspected that the file was corrupt and ran SCANPST on it until it gave me no more errors. I re-processed the file with the same result. Here is what I find in the main-2015-03-03.log file around the time that memory consumption seems to skyrocket:
[iNFO ] 2015-03-03 11:52:07,305 [AWT-EventQueue-0] Logback logging API implementation is configured. [iNFO ] 2015-03-03 11:52:07,305 [AWT-EventQueue-0] Launching Intella Professional 1.7.2-r26532 [iNFO ] 2015-03-03 11:52:07,305 [AWT-EventQueue-0] Detected OS: Windows 7 [iNFO ] 2015-03-03 11:52:07,305 [AWT-EventQueue-0] Detected JVM: Java HotSpot 64-Bit Server VM 1.7.0_45 [iNFO ] 2015-03-03 11:52:07,305 [AWT-EventQueue-0] Max heap size: 1908932608 [iNFO ] 2015-03-03 11:52:07,315 [AWT-EventQueue-0] Library path added: . [iNFO ] 2015-03-03 11:52:07,315 [AWT-EventQueue-0] Library path added: bin [iNFO ] 2015-03-03 11:52:07,315 [AWT-EventQueue-0] Library path added: C:\Program Files\IBM\Lotus\Notes [WARN ] 2015-03-03 11:52:08,134 [swingWorker-pool-2-thread-4] Item uri: aperture://1?/0/ has no data source. [WARN ] 2015-03-03 11:52:08,145 [swingWorker-pool-2-thread-4] Item uri: aperture://1?/0/0/ has no data source. [WARN ] 2015-03-03 11:52:08,155 [swingWorker-pool-2-thread-4] Item uri: aperture://1?/0/1/ has no data source.
...
...
...
[WARN ] 2015-03-03 11:52:11,038 [swingWorker-pool-2-thread-4] Item uri: aperture://1?/2/1561/ has no data source. [WARN ] 2015-03-03 11:52:11,038 [swingWorker-pool-2-thread-4] Item uri: aperture://1?/2/1562/ has no data source.
There are roughly 24,000 messages in this four-second timeframe.