From: Slava P. <sl...@je...> - 2002-03-28 00:07:45
|
This is very strange. The code in question is as follows: int lastLine = Math.min(9,getLineCount() - 1); parseBufferLocalProperties(getText(0,getLineEndOffset(lastLine) - 1)); Buffer.getLineEndOffset() should _never_ return an offset past the end of the buffer. The file size reported by the JVM is irrelevant here. Does this occur randomly, or only with certain files? With files where this occur, are there other problems as well, or is it just this code chunk that breaks? On Thu, 2002-03-28 at 02:36, dmo...@gm... wrote: > Hi Slava, > > starting with jEdit 4.0pre7, I get an ArrayIndexOutOfBoundsException in > Buffer.getText() on _some_ files I edit. This happens when I close and restart > jEdit. It happens in pre8, too. It happens even if started with -noplugins. It > happens _only_ on IBM JDK 1.3.0 and IBM JDK 1.3.1 on AIX, but not on JDK 1.4 > on Windows NT or Windows ME; but I wouldn't write it off as a JDK bug, see > below. > > I attached the full activity log, and one of the files where it happens. > > As you can see from the log, setText() complains about length being > 857669743 chars. Of course the file isn't that long. My guess is that jEdit asks > java.io.File about the filesize during load, and the faulty VM reports that wrong > size. > > However, old jEdit4.0pre6 worked despite of wrong filesize informations, on > the same VM; so it must be some changes inside jEdit. I think jEdit should be > able to cope with wrong filesize informations, as long as the reported > filesize is larger than the actual filesize. > > What do you think? > > Dirk. > > -- > GMX - Die Kommunikationsplattform im Internet. > http://www.gmx.net > > > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > https://lists.sourceforge.net/lists/listinfo/jedit-devel -- Slava Pestov |