Vladimir Kotal

I believe at least one of the allocators I mentioned also works on Windows.

In general, it never hurts to submit a issue for a problem however be prepared you will need to do your homework w.r.t. investigation. The Subversion might be a local...

There is a (clunky) way how to pass username/password to Subversion process - using the `OPENGROK_SUBVERSION_USERNAME` / `OPENGROK_SUBVERSION_PASSWORD` environment variables.

Can you try to get more info about the `IllegalArgumentException` problem ? (i.e. share the contents of the file that seem to cause this)

Is there a stack trace in the log associated with the `IllegalArgumentException` ? The logger used in this case should log one I believe as it is called like this...

Also, maybe worth trying to bisect the original file (assuming the exception is caused by the contents and not the compressed image) and see if you could find the spot...

`2147483647` is `2^31-1`, i.e. 2 GiB short by 1 byte and `abs(-2147483611)` is 2GiB short by 37 bytes so probably overflow of a 2 GiB `signed int` value by 37...

Or perhaps this is actually a bug triggered by file size greater than 2 GiB. `src/main/java/org/opengrok/indexer/analysis/JFlexTokenizer.java` uses `int` for the token offsets within the file: ```java 119 /** 120 *...

In the meantime we could limit the maximum size of files to 2 GiB. Maybe time to revisit #534.

Actually, limiting on input file size cannot work given that how GZip analyzer works - it is based on streams.