Bug 381772

Summary:	Kompare chokes on CSV files differing only in date format
Product:	[Applications] kompare	Reporter:	Dan Dascalescu <ddascalescu+kde>
Component:	general	Assignee:	Kompare developers <kompare-devel>
Status:	REPORTED ---
Severity:	grave
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Kompare kills one CPU core on a 4-core i5 100% CPU usage when comparing these CSVs

Description Dan Dascalescu 2017-06-28 20:54:36 UTC

Created attachment 106361 [details]
Kompare kills one CPU core on a 4-core i5

I have two CSV files that only differ in the date format: YYYY-MM-DD HH:MM:SS vs. M/D/YYYY HH:MM. Kompare appears to higlight intra-line differences, but scrolling is extremely slow and takes 100% of a CPU core.

CompareIt! does the job in half a second.
Diffuse takes 1.5 seconds.
SmartSynchronize takes 4.5 seconds.
KDiff3 takes 25 seconds.
BeyondCompare thinks files are compeletely different
Meld never finishes

Can Kompare do better?

Bugs for the other tools at https://sourceforge.net/p/kdiff3/bugs/217/

Comment 1 Dan Dascalescu 2017-06-28 20:55:17 UTC

Created attachment 106362 [details]
100% CPU usage when comparing these CSVs

Comment 2 Justin Zobel 2022-11-06 09:25:00 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 3 Bug Janitor Service 2022-11-21 05:14:15 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!