This issue is random. I get it around 25% of the time. This bug has been around for a long time (years probably), I just
never got around to reporting it. The data loss caused by this bug is rather minor so I leave it up to you to decide
whether this is a P2 or P3 issue.

Do the following to reproduce the bug:

1) Open a Java file with at least 1000 lines of code (the key is to make sure parsing takes a while) with some of its
imports missing.
2) Issue "Fix Imports" and click OK
3) Before the parser has time to re-parse the file, hit "Fix Imports" again.
4) At this point you will receive the same imports against or (worse yet) some previously resolved imports will now show
up as missing and need to be resolved again.
5) Once you fill out the form and hit OK you will fix the import section is corrupt with contents like this:

------------------------
import javax.imageio.stream.FileCacheImageOutputStream;
import javax.imageio.stream.ImageInputStream;
import nu.xom.Document;

import java.awt.image

 .BufferedImage;

import java.io.ByteArrayInputStream;

import java.io.ByteArrayOutputStreByteArrayOutputStream;

import java.io.IOExceptiIOException;

import java.io.InInputStream;

import java.net.UURI;

import java.util.ArrayList;

import java.util.Collection;
import java.util.CollectiCollections;
import java.util.Iterator;
import javax.imageio.ImageIO;
imimport javax.

imageio.ImageReader;
imimport javax.

 imageio.ImageWriter;

import javax.imageio.strstream.FileCacheImageOutputStream;

import javax.iimageio.stream.ImageInputStream;
impimport javax.

 ws.rs.core

 .MeMediaType;

import nu.xom.BBuilder;

import nu.xom.DDocument;
------------------------

It looks like two race conditions are going on:

1) "Fix Imports" operates on an out-of-date view of the file
2) It looks like two processes are writing into the file at the same time which is why you end up with lines like this:

imimport javax.

imageio.ImageReader;
imimport javax.

 imageio.ImageWriter;