TRACER
  • Introduction
  • Manual
    • About the manual
    • Introduction
      • Text Reuse
      • TRACER overview
    • System prerequisites
    • Download and installation
    • Corpus preparation
    • PoS-tagging, lemmatisation & WordNets
    • Configuration
      • Step 1. Preprocessing
      • Step 2. Featuring/Training
      • Step 3. Selection
      • Step 4. Linking
      • Step 5. Scoring
    • Execution of TRACER
    • Postprocessing
    • Results & computed files
    • Keeping a detection logbook
    • Limitations
    • References
  • Beta
    • Visualising results in a tabular format
    • BabelNet API
    • Text preprocessing automation
  • Support
    • Troubleshooting
      • Unable to parse date
      • Unable to access jarfile
      • Empty score and link files
      • Java lang no class definition found
      • Out of memory
      • Out of bounds exception
      • Windows: length of folder name
      • Windows: PowerShell
    • FAQ
    • Publications
    • Resources
    • Command line: MAC vs. Windows
Powered by GitBook
On this page
  1. Support
  2. Troubleshooting

Out of memory

If TRACER generates an out-of-memory error, the problem is likely caused by the Scoring threshold set in the configuration file. If the Scoring threshold is too low, such as 0.1, TRACER needs more time and memory to compute the results, as a low Scoring threshold leads to a large number of results. To solve the issue, increase the memory value contained in the TRACER execution command from Xmx600m (600 MB of memory) to, for example, Xmx1g (1 GB of memory).

PreviousJava lang no class definition foundNextOut of bounds exception

Last updated 7 years ago