Knowledge Base > IntelliJ Plugin > Troubleshooting


(Please see our separate section for information on Output Codes.)

Structural issues with the project

Please ensure that you are using the Diffblue Cover IntelliJ plugin on a complete project, as the plugin is unable to run successfully if there are flaws in the project structure. Check that:

  • All modules in the project are configured correctly.
  • The project is compilable.
  • The Java SDK version is correct for your project.

Test directories

IntelliJ looks for an existing test source directory. If an existing test source directory cannot be found, it will create one and then notify the user where the tests have been created.

Memory Settings

The Diffblue Cover IntelliJ plugin requires 2GB of memory to run effectively. If you do not have enough memory available, Diffblue Cover will automatically adjust the memory setting. You can undo this change (but please note that your IDE may be unstable without sufficient memory).

If you wish to adjust the available memory manually, please go to Help - Change Memory Settings and amend the Maximum Heap Size to at least 2048, as shown below.

This will update the memory allocation in your .vmoptions file. Please restart your IDE for these changes to take effect.

Error scenarios - inaccessible methods

If you are receiving spurious warnings about inaccessible methods, close IntelliJ and delete the .diffblue index file. A new one is automatically created when the Diffblue Cover IntelliJ plugin is run again.

Error scenarios - inotify watchers

In Linux, Diffblue Cover uses the inotify(7) filesystem API to watch for changes to your class files. If you are receiving an error message about running out of inotify watchers, please follow the advice below to increase the number of watch handles:

  1. Add the following line to either the file /etc/sysctl.conf or a new *.conf file under the /etc/sysctl.d/ directory: fs.inotify.max_user_watches = 524288
  2. Then run this command to apply the change: sudo sysctl -p --system
  3. Finally, restart your IDE. You should now have enough watch handles for IntelliJ to successfully create your tests.


Before beginning the uninstall process, please ensure that no test writing or assertion suggestion tasks are running.