Closed GoogleCodeExporter closed 9 years ago
Thanks for reporting this,
I will see what I can do to get better support for large files. There are some
limitations to the size of the file that can be
opened however as the control I am using requires the entire file to be read
into memory at one time. If the file is a code file
that has highlighting the performance of trying to edit the file once its
loaded into the editor might also be prohibitive.
I have recently re-written all the low level file handling since the last
release version and with the latest development version
was able to open a (130MB, ~1,700,000 lines) test file I made, so this
situation may already be a *little* better. However it
did take about 5 minutes for the file to open and Editra ended up using about
450MB of memory while the file was open.
So I can look into some other possible causes and limitations could you please
provide me with the following information.
1) Does the file you tried to open contain very long lines (+1000 characters
per line)?
2) Type of text in the file (code, plain txt/data)?
3) Do you have Word Wrap turned on in your Preferences?
4) Method of opening the file (command line, Open file dialog, Drag and drop).
5) Amount of memory (RAM) in your computer
Thanks,
Cody Precord
Original comment by CodyPrec...@gmail.com
on 30 Jan 2008 at 12:48
Hi Cody,
here are the answers to your questions:
1) Does the file you tried to open contain very long lines (+1000
characters per line)?
Yes up to about 4000 characters.
2) Type of text in the file (code, plain txt/data)?
It is a log file. Plain text.
3) Do you have Word Wrap turned on in your Preferences?
No.
4) Method of opening the file (command line, Open file dialog, Drag and drop).
Double clicking in the Windows File Explorer -> Open with...
Same effect with opening the file using the Open file dialog.
But using drag and drop it does behave differently: Editra freezes and does not
return.
5) Amount of memory (RAM) in your computer
2 GB
Kind regards
Thomas
Original comment by schwarz....@gmail.com
on 31 Jan 2008 at 11:54
Thanks,
I have found the problem and will try to get this resolved before the next
release version.
cody
Original comment by CodyPrec...@gmail.com
on 16 Feb 2008 at 6:28
Original comment by CodyPrec...@gmail.com
on 7 Dec 2008 at 11:41
This should finally be fixed now for the next release version after 0.4.75.
Initial
testing shows a 10-50x performance improvements.
cody
Original comment by CodyPrec...@gmail.com
on 7 Apr 2009 at 2:30
Wow, that's really useful now in version 0.4.85. Thank you!
Original comment by robert.p...@gmail.com
on 27 Apr 2009 at 8:43
Original issue reported on code.google.com by
schwarz....@gmail.com
on 29 Jan 2008 at 1:04Attachments: