I know there are several threads about this, but I must have not dug deep enough to find the answer. I use Notepad ++ almost exclusively, however, it crashes quite hard when I try to open very large files. We receive files from our mainframe that span anywhere from 1kb-14gb. Notepad ++ has some great functionality that we utilize on these smaller files, however, upon trying to open larger files, we get a hard crash. V or UltraEdit open these files up with no problem, however, it lacks the functionality I desire (or that I'm used to being readily available) in NotePad ++. Any answers, solutions, patches?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did dig a bit deeper and found the "fix" or at least one possible fix by altering the code. Sorry for the additional post that will now show up on searches. If I could delete the originating post I would.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe an user suggested to disable the undo system before opening a file, it seems right now whilst opening the undo buffer is filled aswell, requiring more memory during opening.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know there are several threads about this, but I must have not dug deep enough to find the answer. I use Notepad ++ almost exclusively, however, it crashes quite hard when I try to open very large files. We receive files from our mainframe that span anywhere from 1kb-14gb. Notepad ++ has some great functionality that we utilize on these smaller files, however, upon trying to open larger files, we get a hard crash. V or UltraEdit open these files up with no problem, however, it lacks the functionality I desire (or that I'm used to being readily available) in NotePad ++. Any answers, solutions, patches?
I did dig a bit deeper and found the "fix" or at least one possible fix by altering the code. Sorry for the additional post that will now show up on searches. If I could delete the originating post I would.
Well, how much of a fix is your "fix"? Perhaps the dev and other users might also be helped by it.
I believe an user suggested to disable the undo system before opening a file, it seems right now whilst opening the undo buffer is filled aswell, requiring more memory during opening.