Issue: Eclipse IDE Freezes/Hangs during Indexing of GroupDocs Conversion (Java)

GroupDocs.Conversion Product Family
1

Hello GroupDocs Support Team,

I am writing to report a critical issue encountered while testing GroupDocs.Total for Java for integration into our product. We are currently experiencing severe performance issues specifically within the Eclipse IDE environment.

Current Environment & Setup:

  • Product: GroupDocs.Total for Java (specifically using groupdocs-conversion)
  • Build Tool: Gradle
  • IDE: Eclipse IDE
  • IDE Setting: “Download repository index updates on startup” is enabled in Maven settings.

Issue Description: I have added the groupdocs-conversion dependency via Gradle. The problem occurs when I trigger Auto Import (Content Assist) while editing code, following a Gradle Refresh and Project Clean Build.

At this point, the Eclipse IDE starts indexing to scan the added JAR file. However, the scanning process takes an excessively long time. Even if I attempt to cancel the operation, the indexing process breaks, and the IDE becomes completely unresponsive (freezes/hangs).

This situation repeats every time I clean and build the project, making it impossible to proceed with development tasks.

Question:
Is there a recommended workaround or configuration to prevent this indexing freeze in Eclipse? Since this issue is blocking our development workflow, we urgently need a solution.

Thank you.

2

@dreamsoftware

  1. The Eclipse IDE experiences freezing/hanging during indexing of the GroupDocs Conversion library, particularly when using Java search functionality . Users have reported that the indexing process becomes extremely slow and blocks IDE operations .

  2. A recommended workaround is to disable the “Download repository index updates on startup” setting in Eclipse Maven preferences . This setting can contribute to the excessive indexing load when working with large libraries like GroupDocs.

  3. The issue appears to be more related to Eclipse’s indexing mechanism rather than a problem with the GroupDocs library itself . It is a known behavior when integrating large JAR files into Eclipse projects.

4

I tried disabling the ‘Download repository index updates on startup’ option, but the problem remains the same.

5

Hello @dreamsoftware ,

We’re sorry to hear that you’ve encountered this issue while working with our GroupDocs.Total for Java library.

To better understand the situation, could you please clarify whether you are referencing GroupDocs.Conversion for Java directly in your Gradle file, or if you are using GroupDocs.Total for Java instead?

Additionally, could you let us know what heap space limit is configured for your IDE? We recommend setting it to at least -Xmx2048m.

If possible, please also share a small sample project that reproduces the issue. This would help us investigate your use case more efficiently and provide you with a solution sooner.