failed hash check - Out of memory

[Largo]

Hello,

I have a torrent that Vuze fails to check. I have accumulated lot of torrents in Vuze in the past 7 years, I must say this is the first time this happens.
Vuze is V5.7.3.0 64bits, Windows 10 64bits with 8 Gb of RAM. The computer is pretty much dedicated to Vuze.

Log file was enabled and when I force check that torrent, the log file shows a long list of the same error:
Line 39313: 19:51:08.032 1 disk Piece 0 failed hash check - Out of memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TorrentDM: 'torrent name'
Line 39320: 19:51:08.041 1 disk Piece 1 failed hash check - Out of memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TorrentDM: 'torrent name'
Line 39327: 19:51:08.050 1 disk Piece 2 failed hash check - Out of memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TorrentDM: 'torrent name'
Etc...
I tried a force recheck on about 10 other torrents, some torrents were smaller, but most were bigger or very much bigger than the torrent that fails.
all 10 recheck worked fine (and the log file shows information like Piece 0 passed hash check

This is what I have done so far on this torrent:

• Moved the data (using Vuze's move data command) to another hard drive => move worked fine
  
• added the torrent to 2 other bitorrent clients and did a recheck from each client  => recheck worked fine in both clients
  
• uninstalled Vuze V5.7.3.0 and installed V5.7.4.1 (fresh install + all options left to default), then I loaded my torrent and did a recheck   => failed, same error as before.
  

Since the error seems to relate to "memory", is there any memory-related setting I could adjust?

Cheers,

Largo

[parg]

Check out https://wiki.vuze.com/w/Java_VM_memory_usage - on Windows you can simply increase the amount of heap memory available to Java (and therefore Vuze)

[Largo]

Check out https://wiki.vuze.com/w/Java_VM_memory_usage - on Windows you can simply increase the amount of heap memory available to Java (and therefore Vuze)

 

Hi,
I'm not sure what value are best, so I tried these pair of values (Vuze-> Options -> Startup and Shutdown) :
Max Heap Memory size = 256 MB / 512 MB / 1 GB / 2 GB
Min Heap Memory size = 128 MB / 256 MB / 512 MB / 1 GB 

I restarted Vuze after each change.

but still the same errors.

the torrent details shows that each "piece" is 128.00 MB

Any other suggestion? or maybe better values?

thank you.

[parg]

128MB piece size is totally insane. When downloading you can't share any part of a piece until is has been hash checked, having such a large piece size causes all sorts of inefficiencies. Vuze loads the entire piece into memory to perform the hash check - obviously this would use 128MB of heap memory to do so. I'm not sure why setting the JVM heap size to, say, 1GB, didn't resolve the issue though.

Can you generate a debug.zip file (Help menu, last option, select 'manual send' and email it to me at paul@vuze.com?

Thanks

[Largo]

Hi,
I've been too busy in December to send you the debug file but it is now done.

[parg]

Thanks - I've fixed an internal piece size limit in Vuze that should allow things to work - check out 5741_B13 when it is built in the next few days.

[Largo]

great, I'll wait until 5742.
thank you!