Run time error '35605': This item's control has been deleted about l517 HOT 4 OPEN

I also get this error quite often when trying to process a big list.  Also 
running .994 on win7 x64.  I can reproduce this error at the exact same spot on 
the exact same file everytime (rockyou.txt 136mb file).  It crashes at a little 
over 3.4mil lines with the 35605 error.  One thing I noticed is that when you 
drag a file from explorer into the program it doesn't release something from 
explorer because the pointer stays with the drag n drop icon while the file is 
being imported.  Could the error be a windows resource issue?  Sorry, not a 
windows programmer.

same problem here - win 7 x64
filesize 85MB - crashes after loading about 3.5mil lines and the drag and drop 
pointer
thing...

solution - split file every 3mil words

BUT ! - after trying to append > add to the left/right of string it crashes 
again
with the same error (after loading a 3mil lines file)

I'd like to start off by saying that this is -the- most awesome tool for making 
flexible wordlists.

However, I count myself amongst the crowd that is getting this error when 
building lists over ca. 128mb and/or 3 million words(lines). The direct-to-file 
generation functions of the programs don't seem to crash (i.e. the generate -> 
string to charset functions) however when reloading one of these lists later to 
make mutations or append characters the program will crash with the 
aforementioned error.

I noticed in the Windows task manager that this seems to happen once my machine 
reaches approximately 67% RAM used (4gb available, idling on desktop 29% used) 
and this too is a Windows 7 x64 machine. However, I have used the program and 
had it crash for the same reason on a Win 7 x64 machine with 8gb of RAM.

Recombining word lists is doable with other programs so the bug or crash isnt a 
terrible one but once fixed the L517 tool with be the ultimate one stop shopper 
for making comprehensible lists! Love it!

This is due to the way it's written. It uses ListView to load an entire file, 
once you reach 2Gb of used memory (for the whole process) it will crash. It's a 
limitation set in Windows.
This can be handled if re-written.
I'm actually going to attempt and convert this to VB.NET so I can maybe resolve 
this.