In two quite different environments the very same jEdit version (4.5.2 and using the same jedit4.5.2install.jar in both cases and not using the Mac integration plugin on the Mac) behaves very differently, when opening the same large SQL file.
On Mac OS X (10.6.8) jEdit used approx. 400 MB of heap memory for opening the SQL file, on Ubuntu (10.10) jEdit took 60 MB of heap memory for the same task. I\'ve attached the SQL file (zipped). The problem is not simply with large files or with files that have huge lines (eg. over 200000 character lines). I\'ve created such test files and on both platforms jEdit consumed approx. the same amount of heap space.
Btw. I\'ve used jConsole to monitor heap usage in both cases.
I should also note that on Mac OS X jEdit was executed in a 64 bit Oracle JVM, and on Ubuntu it was a 32 bit Oracle JVM. In both cases I used Oracle JRE 1.6.0.*.
Of course in a 64 bit JRE the same app would eat more memory, but afaik it should not be more than twice the memory used by the app on a 32 bit platform. So the huge difference (6-7 times) in heap memory requirement to open the given SQL file should not be explainable merely by the platform differences.
Any idea what might cause this?
Btw. when opening the SQL file, jEdit asked me whether I wanted to open it without syntax highlighting, or with a simplified syntax highlight or with fulll syntax highlight. I\'ve found that this choice does not affect required heap memory significantly in either case.
If more info is needed (any debug logs, etc.), I\'d happy to provide them.
P.S.: Sourceforge does not allow attachments larger than 256K at the moment. And since the problem occurs only with large files, I uploaded my test SQL file to somethere else: http://dropcanvas.com/h7nbd
This will be only temporary (I guess dropcanvas won't keep my upload "forever"), but if you suggest another method for sharing my test SQL file, I'll gladly upload it again.