Perforce QAC Eclipse IDE Known Issues

The following list summarizes extant issues within Perforce QAC Eclipse.

  • The memory requirements for Perforce QAC Eclipse have increased. In order to prevent Out of memory issues, it is required to increase memory allocated to JVM to at least 512 megabytes by setting -Xmx512m flag in eclipse.ini file. Please refer to https://wiki.eclipse.org/FAQ_How_do_I_increase_the_heap_size_available_to_Eclipse for more information.
  • On Red Hat Enterprise Linux 6, Eclipse may crash in different circumstances both with and without the plugin. To prevent this crash, it is required to add -Dorg.eclipse.swt.internal.gtk.cairoGraphics=false to eclipse.ini file. Please refer to https://www.eclipse.org/forums/index.php/t/834565/
  • On Red Hat Enterprise Linux 7, Eclipse may not show partially or completely the content of the window. To prevent this problem in Eclipse versions up to Luna, it is required to run export SWT_GTK3=0 before starting Eclipse. However, to prevent this problem in Eclipse Mars it is required to add –launcher.GTK_version 2 to eclipse.ini. Please refer to https://bugs.eclipse.org/bugs/show_bug.cgi?id=470944
  • Opening a file with a large number of diagnostics can cause severe reduction in Eclipse performance. This Eclipse known issue (Bug 402752 - Performance regression in marker update handling) is most likely to happen if Scalability mode has to be activated (by default when opening a file containing more than 5000 lines).

  • Perforce QAC product testing uses a source code project configured with correct encoding to test display of the full Japanese kanji character set. Display of these characters is garbled as of Eclipse 2022-06, with no workaround. Reproduction does not require any Perforce QAC software to be installed. The issue is similar to https://bugs.eclipse.org/bugs/show_bug.cgi?id=547228 but does not require the user change encoding in the IDE for any source file, rather the encoding defined in the preferences file is ignored by the IDE.