You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use WinMerge, I found that WinMerge crashes in certain circumstances. This are really huge bug. I hope you can fix then as soon as possible.
When I compare a lot of files (More than 1000) and the total size of them is more than 2 GB (such as lots of photos, lots of music files, lots of video files and so on). such as this:
When I compared these files in two folders and I found the different files, I used the function "copy" to make the two folders' files the same. and I copied more than 8 files.
However, When I clicked the "Yes" button on the picture above, the WinMerge crashes, and it uses lots of CPU. And I don't know why.
This does seriously affect normal use, especially when there are very many files.
When I use WinMerge to compare two files whose content is not regular. (Such as two video files, two music files, two EXE files, two ISO files and so on).
And I previously opened them with Notepad++, and the Notepad++ didn't crashes.
It is certain that I only want to know whether the two files are same or not.
However, the WinMerge crashes for a long time when comparing these two files. especially when the two files are relatively large (More than 30 MB). And it also uses lots of CPU.
This does seriously affect normal use, too. And It makes WinMerge unable to compare most types of files that is relatively large.
The WinMerge version I used are both the 2.16.4.0 (64bit) and the 2.16.5.0 (64bit). Both of them have these two problems. It seems that you didn't fix this problems in the new beta version.
I can give you one tip: You can add a progress bar (进度条) or "loading" where the WinMerge is working hard in order to avoid crashes.
In all, These two bugs are all very serious, and seriously damaging the user experience. I hope you can fix them as soon as possible. Thank you.
The text was updated successfully, but these errors were encountered:
I frequently compare two folder structures, each containing over 200,000 files (in 2,700 folders) totaling more than 180 Gigabytes. These folders contain a random mixture of text, video, pictures, source code, executable files and other binary files. The largest file is 2.8 Gb.
I often use “the Copy function” to make the structures become more identical.
I have never encountered a problem similar to your problem Very small fixes #1.
Regarding your problem Corrections and Add translations (Portuguese) #2… Directly comparing two “large” files (typically larger than 50 Megabytes (but that is a very fuzzy boundary)) has always caused extreme resource consumption (memory and elapsed time). This became more obvious when WinMerge began allowing files larger than 2 Gb (precisely: 2^31 bytes or larger). I committed some patches a few years ago in an attempt to minimize this problem; alas, they made some things “worse”, and they were eventually removed. Note that this problem does not impact “folder comparisons” that contain large files within the folder tree, only direct “file comparison” of two (or three) large files.
While I am sure that there is a fix for this problem, I am also sure that it will be reasonably difficult. ☹
When I use WinMerge, I found that WinMerge crashes in certain circumstances. This are really huge bug. I hope you can fix then as soon as possible.
When I compared these files in two folders and I found the different files, I used the function "copy" to make the two folders' files the same. and I copied more than 8 files.
However, When I clicked the "Yes" button on the picture above, the WinMerge crashes, and it uses lots of CPU. And I don't know why.
This does seriously affect normal use, especially when there are very many files.
And I previously opened them with Notepad++, and the Notepad++ didn't crashes.
It is certain that I only want to know whether the two files are same or not.
However, the WinMerge crashes for a long time when comparing these two files. especially when the two files are relatively large (More than 30 MB). And it also uses lots of CPU.
This does seriously affect normal use, too. And It makes WinMerge unable to compare most types of files that is relatively large.
The WinMerge version I used are both the 2.16.4.0 (64bit) and the 2.16.5.0 (64bit). Both of them have these two problems. It seems that you didn't fix this problems in the new beta version.
I can give you one tip: You can add a progress bar (进度条) or "loading" where the WinMerge is working hard in order to avoid crashes.
In all, These two bugs are all very serious, and seriously damaging the user experience. I hope you can fix them as soon as possible. Thank you.
The text was updated successfully, but these errors were encountered: