Hi Harry,
I can confirm this bug on Windows only. It doesn't happen on the rest of platforms.
Sometimes (most times) when one opens a tool window from any workspace different from the first workspace (Workspace01), an access violation error message is shown. Then the tool opens and continues working normally. This is a regression in version 1.6.9.
As far as I have tested, this bug is nasty but actually harmless. After the access violation error, everything continues working. Sometimes a fake 'Out of memory' message is also shown, but it can be safely ignored (there is actually no out of memory condition).
The good news is that I have managed to fix this bug (after a 'nice' afternoon of hard debugging sessions). I'll publish an update to the Core application as soon as possible.
Workaround: Try to work in the first workspace. If you see one of these access violation errors, just dismiss the error messages and continue working normally.
Sorry for ending the year with such a nasty bug...
