This doesn’t look like any known issue. If you could share a sample project that would allow reproducing the issue on our side, we should be able to fix this.
No problem. As long as the problem is caused by one of the VisualGDB components and we get enough details to reproduce it on our side, we are usually able to fix it very quickly.