It can handle file sizes up to the largest contiguous chunk of 32-bit virtual memory
That makes sense for the 32 bit version of TextPad, but it doesn't make sense for the 64 bit version, for which 4GB seems like an arbitrary limit.
Unless someone can point out why it's not?
bbadmin wrote:The 32-bit file size limitation (4GB) does not apply to the 64-bit edition.
However, it still needs to allocate the entire size in virtual memory.
That needs to be clearly stated in the TextPad specs page otherwise someone looking for a text editor that handles very large file will read that TextPad can only handle max size 2GB files and move on.
I'm finding that whilst a 12GB CSV text file can be opened by 64-bit TextPad 7.4 and a search a replace performed successfully, saving the file results in a empty file on disk. The file save progress moves to about 30% and then quietly "dies".
For info, my PC is an Intel Xeon workstation with 16GB RAM and I'm not running anything else other than an instance on Win File Explorer.
I've opened multi GB files in TP as well. It's all a resource issue. I mean if you have 4 TB of RAM and 10 PB of disk space, you won't even blink when you open a 4 GB file.
kengrubb wrote:I've opened multi GB files in TP as well. It's all a resource issue. I mean if you have 4 TB of RAM and 10 PB of disk space, you won't even blink when you open a 4 GB file.
Have you tried editing said opened file (i.e. making a small change on most lines of the file) and then saving it?
I've resorted to using another editor which can handle large files (12GB) not problem, so I doubt the problem I described in my earlier post is completely resource related.
