Attached is a file that successfully replicates this
bug on my machine. The noteable characteristic of this
file is a ridiculously long line. It will load up fine
in notepad, however, and can be rendered in a browser
even. Not so with JEdit, which stops responding, but
still uses up CPU time. I'm sure this isn't a plugin
issue, I've tried opening it without the html
extension, and also disabling my plugins. I'm running
Win2K, if you have any problems replicating this.
Logged In: YES
user_id=1253354
While I was submitting this bug, the JEdit started
responding again(after a long time). However, with a file
in excess of 100kb, I've had JEdit run for over 10 mins
without finishing the load. So, you can experiment with
different lengths, but this is still a bug.
Logged In: YES
user_id=1304219
Your attachment took about two seconds to load on my
machine, a Pentium M 1.6 GHz.
Logged In: YES
user_id=663176
I think this might be related to what the TaskList plugin
(0.4.4) is doing, when it gets (de-)activated in the
plugin manager, because I get the same delay (about
10 seconds) then like with starting jEdit or (in particular)
resizing the textarea.
jEdit CVS, Sun Java 1.5.0_04 (Linux86), amd64.
Logged In: YES
user_id=1486645
Originator: NO
The Bug occurs with this system:
Win2k SP4, java 1.5.0_08, jEdit 4.2final
The Bug does NOT occur with these systems:
Win2k SP4, java 1.5.0_08, jEdit 4.3pre9
WinXP SP4, java 1.5.0_10, jEdit 4.2final
WinXP SP4, java 1.5.0_10, jEdit 4.3pre9
I was able to open this in less than a second and it was also being parsed by XML sidekick.
I think your heap size was too small.
Increase it to something with a couple of hundred megabytes in it, to help it fit the thing in memory.
Especially if it needs to be parsed by a plugin, that needs even more memory.
export JAVA_HEAP_SIZE=450
exec java "-Dawt.useSystemAAFontSettings=on" "-Dswing.aatext=true" "-Djedit.home=$JEDIT_HOME" -mx${JAVA_HEAP_SIZE}m ${JEDIT} -jar "$JEDIT_HOME/jedit.jar" -reuseview "$@"
oh, i forgot to say, I'm using SVN versions of XML (2.5) and jEdit (4.4pre1)
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).