Crash at 93% loading 1.4GB text file about glogg HOT 5 CLOSED

I'm having the same problem with a 62 GB file on Win 7 x64. Get's to 26% and then throws the same error. Unfortunately there's some sensitive data in the file so I probably won't be able to upload it.

from glogg.

Same problem for me with an ~ 800MB file that contains 86,453,666 lines (wc utility is your friend).
Crash at 76 % with "This app has requested the runtime to terminate ..."

When attaching a debugger before the crash, I get the following output in the debugging window:

Invalid parameter passed to C runtime function.
Invalid parameter passed to C runtime function.

The call stack of the crash (abort() really) is at:
...
msvcrt.dll!_abort() + 0x26 bytes
QtCore4.dll!6a3d6c6d()
...

Since I don't have symbols for the QtCore4.dll you ship, I can't investigate further atm.

Looking at the memory consumption of glogg.exe, Virtual Size is at 675MB and Working Set is at 570MB, so it would seem that it's not directly memory related, since there is sstill headroom for a 32bit process with these values.

from glogg.

Thanks for all the reports, I think I do understand the issue now, this is a lack of memory condition when creating the index which for some reason is not caught by the current code. I'll try and fix that quickly. The problem is the size of the index (8 bytes per line) effectively put a limit on the size of files that can be loaded. Maybe we could consider working without an index if the file is really big, but it's difficult to maintain all functionalities....

from glogg.

I think you should consider moving the tool to 64bit, that way, only the physical memory would limit the tool. Have you ever tried compiling it for 64bit? Were there any problems?

from glogg.

This should have been fixed a while ago.

from glogg.