Interface.exe crash 2016-01-13


#1

It’s crashing at startup, started again. it workfine. did update it crash at start. But then the second start it seems to work fine. Well here some error line

Faulting application name: interface.exe, version: 0.0.0.0, time stamp: 0x56959945
Faulting module name: Qt5Core.dll, version: 5.5.1.0, time stamp: 0x561c0647
Exception code: 0xc0000005
Fault offset: 0x0000000000124f53
Faulting process ID: 0x924
Faulting application start time: 0x01d14e4f8789cb90
Faulting module path: :\Program Files\High Fidelity\Interface\Qt5Core.dll
Report ID: af8399e0-6cc7-439a-b1b0-c8704f9b68c8

Faulting application name: interface.exe, version: 0.0.0.0, time stamp: 0x56959945
Faulting module name: Qt5Widgets.dll, version: 5.5.1.0, time stamp: 0x561c07c8
Exception code: 0xc0000005
Fault offset: 0x0000000000038303
Faulting process ID: 0x2754
Faulting application start time: 0x01d14e4fc4bb54ff
Faulting application path: :\Program Files\High Fidelity\Interface\interface.exe
Faulting module path: :\Program Files\High Fidelity\Interface\Qt5Widgets.dll
Report ID: 54bffaaf-490c-4b92-a622-644af432d54a

Faulting application name: interface.exe, version: 0.0.0.0, time stamp: 0x5696b9b7
Faulting module name: ntdll.dll, version: 10.0.10586.20, time stamp: 0x56540c3b
Exception code: 0xc0000374
Fault offset: 0x00000000000ee00c
Faulting process ID: 0x1c78
Faulting application start time: 0x01d14e4feaa73992
Faulting application path: :\Program Files\High Fidelity\Interface\interface.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 1ae17a18-3a14-408b-83c2-d7b301c8d52e

The visual studio error is generated from the exe package from interface.exe


#2

Interesting. I just installed 3908 (latest) interface and it works OK; that is, it does not crash on launch. Your crash has the ear markings of mismatched DLL files. My suggestion to you (and this is overkill) is to uninstall interface and the stack manager entirely. Restart your computer, then install anew. That process clears installation mismatch problems.

If after doing that you still find interface crashing at launch, then there probably is some other left over Qt junk that may need manual cleanup.


#3

I wish i coud uninstall, but the need to fix the uninstaller first ! Or mabye let the installer do a repair.
I cannot uninstall interface.exe it’s just freezing and no uninstall.
Aska while ago for the correct registery settings so i can check / remove it and uninstall it that way.


#4

Ok, i did go one level high. booted windows 10 in safe mode. There i can uninstall it. But as soon i have installed a fresh one in normal mode and click uninstall, forget it. Still think it’s a combination windows 10 + High Fidelity that refuse to uninstall.

Well i have at least now a fresh installed interface.exe with old ini file. no fun to delete that. Sofar it seems fine. time will tell.


#5

I can attest it is not that combination in general because I have uninstalled interface several times on Win10Pro during a spate of version testing.

Forgive me if this sounds basic: are you uninstalling interface via the control panel, 'Programs and Features"? Or, are you launching the uninstall.exe app directly out of C:\Program Files\High Fidelity\Interface?

[Edit] I was going to suggest using WMIC to uninstall interface, but it is not registered as a package.


#6

In the process of trying to reproduce this problem and @ctrlaltdavid 's menu/crash problem I ran into various non-deterministic crashes that have been reported repeatedly for several months now, in which: dde was left running in zombie mode but interface quit/crashed. interface left in a compute loop semi-crash. And subsequent installs jammed until I manually cleaned up. It is not really possible to attribute a cause to a problem because there are so many unfixed and longstanding bugs in this area.

This POS interface and lack of QA on it goes beyond unacceptable. I’m done being Cassandra QA. Fix your damn crap, people. Fix it soonest because it has fallen below alpha level.


#7

Both, not make any difference. The both hang in endless loop. the uninstaller seems not to appear in the list too. sometimes it does.

Just tried it from the windows uninstaller. it’s not working. nothing happens. except the uninstaller process seems busy if you click uninstall again. Also i cannot find any uninstall process that is running in the task manager !

The problem btw started to appear since or after interface.exe is 64bit.

Also interface.exe never get installed in the C: drive, and i will never do, it’s on other drive.

And after a correct shutdown, and a new start. interfeace.exe crashed again.

Faulting application name: interface.exe, version: 0.0.0.0, time stamp: 0x56972cf3
Faulting module name: Qt5Qml.dll, version: 5.5.1.0, time stamp: 0x561c0990
Exception code: 0xc0000005
Fault offset: 0x000000000016a6fc
Faulting process ID: 0x2640
Faulting application start time: 0x01d14ed3ee930c3a
Faulting application path: :\Program Files\High Fidelity\Interface\interface.exe
Faulting module path: :\Program Files\High Fidelity\Interface\Qt5Qml.dll
Report ID: 459926d6-5953-4d22-97c7-21b4db932f03


#8

Interface.exe is still crashing at startup sometimes.

Faulting application name: interface.exe, version: 0.0.0.0, time stamp: 0x56972cf3
Faulting module name: Qt5Widgets.dll, version: 5.5.1.0, time stamp: 0x561c07c8
Exception code: 0xc0000005
Fault offset: 0x0000000000038303
Faulting process ID: 0x14f0
Faulting application start time: 0x01d14f9402bc3c42
Faulting application path: :\Program Files\High Fidelity\Interface\interface.exe
Faulting module path: :\Program Files\High Fidelity\Interface\Qt5Widgets.dll
Report ID: d1c47be9-b437-4550-9d7d-9345ecabd6a6
Faulting package full name:
Faulting package-relative application ID:


#9

@Richardus.Raymaker, I had a similar problem back when the shift from x86 to x64 interface happened. I ended up digging around to the Program Files (x86) folder, finding the interface folder and ran the uninstaller.exe file in there. That removed the junk that the 64-bit installer failed to remove. Try that.


#10

Already did a safe mode uninstall and reinstall in normal windows. SO that is not fixing the problem.


#11

Why there’s zero reason to bother reporting bugs anymore.

No access even as read only to closed bug tracking system. [An odd thing for a supposed open-source project that supposedly wants people to help shake out the bugs.]

No feedback on bug reports means they don’t care to bother with. This leads to a general feeling of why bother as you have no idea if it’s worth time to document bug and give reproduction case.

Over time you just stop giving a damn or you forget something has been reported before (sometimes even by self) and bring it up again only to see it ignored again. You know like…

Interface doesn’t terminate cleanly in various conditions.

Interface makes bogus useless HTTP requests.

Audio tries opening hardware with invalid/impossible latency settings and then says device can’t support sample rate so engages re-sample code.

And at least a dozen more things I used to have notes about that I finally sent to recycle bin.


#12

Maybe then it is time to put up an alphas bug reporting system, Mantis or whatever people like. AT least that way the unaddressed bug reports will not get lost. I’m in the middle of a noise monitoring project, so no bandwidth to do this. Anyone else want to volunteer?


#13

I got HiFi working few months back but haven’t had time to mess around, redownloaded the latest files and installed and uninstalled rebooted etc yada yada and everytime I run interface.exe it crashes