Bug 340485 - Check sum does not like working with 4 files large files
Summary: Check sum does not like working with 4 files large files
Status: ASSIGNED
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 2.2.0
Platform: Other Microsoft Windows
: NOR grave
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-30 00:55 UTC by Kevin Jaeger
Modified: 2017-01-17 21:33 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Jaeger 2014-10-30 00:55:55 UTC
OS: Windows 7/32 [totally up to date 30th Oct]
COMPUTER: Toshiba Satellite Pro 4 GB ram
DISK: 1 hard disk, partitioned C, D [90% free and 95% free]

I can run the checksum tool on two files from the list below and it works great. As soon as I go to run the 4 files simultaneously the program crashes.  

Error Message: Failed to move file D:/Software/Checksum/sha1sum.txt to its final destination, sha1sum.txt: Error during rename. File that was generated: sha1sum.txtHp4872.new [o bytes]

I have copied the folder from D: to C: by dropping it on desktop, with same error occurring.

FILES BEING CHECK-SUMMED:
BobCAD_V27_Release_x64(1).exe . . 642 MB
BobCAD_V27_Release_x64.exe . . . . . 642 MB
The other 2 files are the x86 versions at 620 MB each.

The files have no errors and work fine with other checksum tools. Individual checksums are same as those generated by other tools.

It seems to me that the size of the task [gigabytes] is the problem, because it will generate checksums for 10 small files without error.

Reproducible: Always

Steps to Reproduce:
1. high light files in same folder
2. right click for checksum option
3. left click checksum and wait for error

Actual Results:  
See above, the 3 steps are detailed

Expected Results:  
Error Message: Failed to move file D:/Software/Checksum/sha1sum.txt to its final destination, sha1sum.txt: Error during rename. File that was generated: sha1sum.txtHp4872.new [o bytes]

Generate checksums for each of the 4 files and written them to a text file.
Comment 1 Rafail Ahmadisheff 2015-03-07 21:47:42 UTC
I'm facing that same issue with Kleopatra. (Windows 7 HP 64-bit). I actually installed Gpg4win 2.2.3. The error messages that I get read as follows: "Failed to move file C:/b/the-full-path/sha256sum.txt to its final destination, sha256sum.txt: Error during rename." An empty file named "sha256sum.txtHp6836.new" gets created in the target folder. I get the error regardless of whether I invoke the checksums calculation from context menu in explorer (GpgEX) or from the File menu in the main Kleopatra window. The error seems to occur on folders that have more than 2 GiB of data in them. I have successfully created and verified checksum files for folders of smaller size.
Comment 2 Andre Heinecke 2015-09-10 18:49:05 UTC
Thanks for your reports. I can reproduce the problem using a single 11gb file. Strangely enough signing that same file works and running sha1sum from gpg4win also works.

Looks like some timeout in kleo.
Comment 3 Stefan 2017-01-17 21:33:47 UTC
I can reproduce, especially comment 1:
Kleopatra
Version 2.2.0-gitfb4ae3d (2015-11-12)
Unter KDE 4.13.3
on Windows 10 64bit (Pro), should be up to date as of 2017-01-17
Intel Core i5-4670K @ 3.4 GHz

sha256sum.txtHp2692.new
sha1sum.txtHp8528.new
are generated for a 3.91 GB large file (4102945 KB), moving file to sha256sum.txt failed: Error renaming the file.

Unfortunately the executables seem single threaded. Running "sha256sum.exe filename.iso" directly in the windows commandline gives me a checksum after 42 seconds. So it is difficult to look for a timeout. One core of my system is on 100% load. Moving the large file to an SSD does not speed this up. So I can't easily test if it is a time out or a file size problem.

From a 1.67 GB (1758561 KB) large file the checksums are correctly calculated and saved.
From HDD:
sha256sum.exe has a run time of ~19 seconds
From a USB thumbdrive on USB3: 19 seconds
Same drive on USB 2: 44 s
Kleopatra on USB 2: could not move file after 32 seconds

But Window's USB-File-Caching let's me successfully finish a second run on the same file in under 30 seconds. (To avoid the use of cached thumbdrive data, I did my test always on a freshly plugged in drive and verified the read speed in the Windows Resource Monitor.)