0 Members and 1 Guest are viewing this topic.
This will be fixed by another beta refresh, probably tomorrow.Sorry for the trouble.
Please update to the latest build (668) - should have the problem fixed.
Perhaps you need to change the Original Post topic since 5.0.668 resolves this memory leak or add [Resolved] at the end of it.