wiki:ReportingABug

How to Submit a Bug Report

Submitting good bug reports is very important.

Before you Submit any bug

  • If you're reporting a bug in I2P,
  • If you're having a problem with the Debian or Ubuntu package, check to see if a new package has been uploaded (sudo apt-get update && sudo apt-get upgrade). If not, continue.
  • If you're experiencing very high RAM or CPU usage:
  1. Make sure you're using a recommended version of Java. Oracle Java Version 7, OpenJDK 7, or IcedTea7 are recommended for most systems. On the Raspberry Pi, use Oracle JDK 8 (with JavaFX) for ARM Early Access. PowerPC users should try IBM SDK 7.
  1. If you're running plugins such as Seedless or I2P-Bote, try disabling them to see if the problem goes away. In some cases you may need to restart I2P after disabling the plugin.
  1. If I2P is crashing/restarting, check the logs to see if you're having OOM (Out of Memory) issues. By default, I2P is limited to using 128 MB of RAM. If you have a high bandwidth router or are running multiple plugins you may need to allocate more RAM to I2P. See OOM.

  • If your bug is for something other than a problem in third-party plugins (new features, improvements, etc.), follow the steps below.

Steps for Bug Report Submission

  1. Search for existing bug reports, in order to avoid submit a ticket for a problem that we already know about. You're welcome to add additional information to an existing ticket if you think it would help us fix the problem.
  1. Create a new ticket. To file a new ticket, you'll need to log in or create an account first. Any accounts created before October 11, 2013 have been deleted—if you have not logged in since then, please re-register.

It is important that you include as many details of the bug as you can. If reporting a bug in I2P, include the version information located at the top of http://127.0.0.1:7657/logs in any ticket filed.

Obtaining a thread dump

If asked to obtain a thread dump, the following steps will help you do so.

  1. If you can access the router console (usually at http://127.0.0.1:7657), go to the service tab. In the Debugging section will be a Dump Threads button. Click it.
  1. The thread dump will be visible in the wrapper.log file. The location of wrapper.log will also be listed on the router console's logs page.
  1. Copy & paste the thread dump to http://pastethis.i2p, noting the URL in the ticket, or attach a file with the thread dump to the ticket.

If you cannot load the router console and you're running Linux, OSX, *BSD, or Solaris, try running i2prouter dump to dump the threads to your wrapper.log.

Last modified 5 years ago Last modified on Oct 21, 2013 6:03:36 PM