Hi, thanks for sharing this.
Wow, that's a lot of memory consumption!
We don't have any leak that we know could cause this ... so we'll need to get more detailed information to figure this out. The next time this happens to you, could you do the following?
- Submit a bug report. The log file will give us some information about what the engine is doing, even if it'll only be the tail end of it.
- Check the processing queue to see what the engine is trying to do. Is there anything interesting about the tasks it's running?
- Perform an export of the timeline report using the Tests Window. If you can share this with us (send it via the
contact form), we'll line it up with the bug report and try to figure this out.