Bug 459484 - Crash and Windows SmartScreen warning
Summary: Crash and Windows SmartScreen warning
Status: REPORTED
Alias: None
Product: kdiff3
Classification: Applications
Component: application (show other bugs)
Version: 1.9.6
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: michael
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-21 10:01 UTC by malte.meister
Modified: 2022-12-14 15:16 UTC (History)
1 user (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 malte.meister 2022-09-21 10:01:54 UTC
SmartScreen flagged the installer, but more importantly 1.9.6 crashes on start with the following being recorded in the event logs:

Faulting application name: kdiff3.exe, version: 0.0.0.0, time stamp: 0x62ba2817
Faulting module name: Qt5Core.dll, version: 5.15.2.0, time stamp: 0x61841ffd
Exception code: 0xc0000409
Fault offset: 0x00000000000205b8
Faulting process id: 0x57c4
Faulting application start time: 0x01d8cd9b43f9b3a4
Faulting application path: C:\Program Files\KDiff3\bin\kdiff3.exe
Faulting module path: C:\Program Files\KDiff3\bin\Qt5Core.dll
Report Id: 003676c4-7e46-4462-95a9-9a6d8b6df20a
Faulting package full name: 
Faulting package-relative application ID: 

SOFTWARE/OS VERSIONS
Windows: 10 Pro 21H1 (Build 19043.2006)

Reverted to 1.9.5 which is working fine. Let me know if/how I can assist in diagnosing.
Comment 1 michael 2022-10-18 16:30:42 UTC
Interesting what is the md5 for that 1.9.6 installer should be fc73998a08d55234f9e79d90261bd0eb?
Comment 2 malte.meister 2022-10-24 10:26:44 UTC
(In reply to michael from comment #1)
> Interesting what is the md5 for that 1.9.6 installer should be
> fc73998a08d55234f9e79d90261bd0eb?

Unfortunately I didn't keep the 1.9.6 installer that I had downloaded originally, but unless it was updated on the KDE download site (judging by the last modified date there, it wasn't) I think it's unlikely I had a different/corrupt installer.

I just installed 1.9.6 again having re-downloaded and verified the MD5 of the installer. Now:
- The installer is no longer flagged by SmartScreen (having recently experienced something similar with the installer of another application, this could just mean that a false positive has been corrected by Microsoft).
- The app still crashes on start as before.
Comment 3 michael 2022-10-24 17:09:36 UTC
Thanks. Just wanted to be sure. I had a feeling the smart filter flag was a false positive. Nice to see it was corrected so quickly. Going need someone with more windows experience to trouble shoot this further.
Comment 4 Nikolai Rogalskii 2022-11-10 22:18:14 UTC
Hi,

I also unable to start Kdiff3 v1.9.6 in windows 10.

I've installed it with command:  winget install -e --id KDE.KDiff3

In "Event Viewer" i see such log: 

Faulting application name: kdiff3.exe, version: 0.0.0.0, time stamp: 0x62ba2817
Faulting module name: Qt5Core.dll, version: 5.15.2.0, time stamp: 0x621e8a1b
Exception code: 0xc0000409
Fault offset: 0x00000000000205a8
Faulting process id: 0xb3ac
Faulting application start time: 0x01d8f550612390dd
Faulting application path: C:\Users\nrogalskiy\AppData\Local\KDiff3\bin\kdiff3.exe
Faulting module path: C:\Users\nrogalskiy\AppData\Local\KDiff3\bin\Qt5Core.dll
Report Id: 2c2415cd-091a-4d28-a3c0-487ca677e9f3
Faulting package full name: 
Faulting package-relative application ID: 

OS Version: 
Windows 10 Pro 22H2 (Build 19045.2251)


---

As workaround I've downgraded to previous version with command winget install -e --id KDE.KDiff3 -v 1.9.5
v 1.9.5 is working fine
Comment 5 michael 2022-11-12 22:45:14 UTC
Can someone who is able to reproduce this get an actual stack trace. Just knowing that it's crashing somewhere in qt4Core isn't perticular helpful. It could be anything.
Comment 6 malte.meister 2022-12-14 15:16:56 UTC
(In reply to michael from comment #5)
> Can someone who is able to reproduce this get an actual stack trace. Just
> knowing that it's crashing somewhere in qt4Core isn't perticular helpful. It
> could be anything.

Yeah, I tried attaching a debugger some days ago but ran into some problem. Will try again when I find some time.