From time to time when using CSIDE the java system craps out. Sometimes it's recoverable but other times it's best to reboot the VM you are using. My problem is that the Ospace search function spins endlessly at 0% after such a java crash and even rebooting the vm doesnt clear it. There must be a setting in a file somewhere that is wrong/corrupt and it's persisting through a VM reboot. Any tips on where I can look? I dug around in the workspace folder but found nothing that looks like it's related to search.
In the Module Explorer I right click and search, make my selections and start it and it stays at 0% forever, returning no results.
