bantar

OK, finally installed 0.94 Build 5265. App is working ok, but after a while it crashes. I'm seeing the same 3 crashes when it happens. Happened twice now. This time, it has crashed while in the foreground, but not while actively making changes. See the crash logs screenshots and logfile.flirc20230124.log flirc20230124.txt

Seeing your profile issue noted prior to me installing, I chose to create a brand new profile. I installed on that profile, so I don't expect a corrupted profile. It exists for the sole purpose of testing Skip. I do have BitDefender installed, but nothing ASUS related. I'm on a Dell Laptop. It's easy enough to disable BitDefender to see if anything changes. I've never downloaded the software from the website, because I didn't know where to look. Was looking on the forums page. I can try it when I get home. I loaded 5276, and when poking around, it wanted to update to 5293. When that happened, no connections to the remote were possible. Downgraded to 5276 and it worked fine. I wonder what version is on the website? I'm guessing 5293. Secondly, I've not tried a clean install of 5293 either.

The download site is located here: https://flirc.tv/products/skip1s-remote?variant=43489094729960#spec2

There might be a disconnect, with respect to the issues that I'm reporting. I'm only seeing the app crash in the background. The detection of the remote is working with build 5276, but not with 5293. When I rolled back to 5276 remote detection returned. With remote detection, I've seen these behaviors: 1) Start the app, connect the remote, detected. 2) Remote connected for some time, start the app, not detected. Disconnect and reconnect the app, remote is detected. I'm assuming that this is expected behavior, and if not, presented here. 3) When app crashes, for about 5 minutes (or less), the remote attempts to reconnect (hear the dings from windows as it connects/disconnects). Do you need more from me given this clarification?

Part 3 of 3 662858281_RegistryEditor2023-01-2122-14-35.mp4

Registry Editor 2023-01-21 22-13-41.mp4 Part 2 of 3

I'm using Bitdefender Total Security. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class contents: 631816196_RegistryEditor2023-01-2122-13-41.mp4

Is Sentry a debugging tool that we need to install? And to be clear, crash means the GUI disappeared. No error dialogs of any kind captured the moment. The only clue is a missing app. It's not running in the task list and each time, I'm finding a corresponding crash event in the windows logs. Other point to note, is that I've never seen it crash while actively using it.

One more observation.... After crashing, the remote would connect and reconnect multiple times, then eventually give up. Presented in case this is not normal behavior. I did try multiple cables and verified that neither of these cable connections were the cause of the connect/reconnect.

And a different crash: Faulting application name: SkipApp.exe, version: 0.1.0.5276, time stamp: 0x63c45afd Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x5b7d4d22 Exception code: 0x00001007 Fault offset: 0x000000000010fe32 Faulting process id: 0x48dc Faulting application start time: 0x01d92c84a4863d99 Faulting application path: C:\Program Files\WindowsApps\1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5276_x64__sddpyax1dmvqm\SkipApp.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 321bfd1f-a5a0-4a4c-928c-370f79ae4500 Faulting package full name: 1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5276_x64__sddpyax1dmvqm Faulting package-relative application ID: App

But still crashes while not actively interacting with the app. Faulting application name: SkipApp.exe, version: 0.1.0.5276, time stamp: 0x63c45afd Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x5b7d4d22 Exception code: 0xc000027b Fault offset: 0x000000000010fe32 Faulting process id: 0x6a6c Faulting application start time: 0x01d92c83d5b26768 Faulting application path: C:\Program Files\WindowsApps\1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5276_x64__sddpyax1dmvqm\SkipApp.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 4c7e726e-e4f3-4d22-9bef-8b80920e4378 Faulting package full name: 1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5276_x64__sddpyax1dmvqm Faulting package-relative application ID: App

Build 5726 connected and sync'd and turns the tv on and off!

EDIT: Updated crash data First time install using build 5276 that later auto updated to 5293. Using Windows 10 22H2 Build 19045.2486 on a Dell Laptop. Created a new user profile just for this. App installed ok, loaded ok, seems to work ok, but the Remote never connects. Says Offline. I found this error in the Windows Log: Event 10016, DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user BRIAN-ON-THE-GO\FLIRC SID (S-1-5-21-3984057536-428044359-1120404447-1004) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. The App is crashing on occasion. So far, each time it happened, I was doing something else other than having the app in the foreground. Faulting application name: SkipApp.exe, version: 0.1.0.5293, time stamp: 0x63c6dd76 Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x5b7d4d22 Exception code: 0xc000027b Fault offset: 0x000000000010fe32 Faulting process id: 0x690c Faulting application start time: 0x01d92c7f9671a5d1 Faulting application path: C:\Program Files\WindowsApps\1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5293_x64__sddpyax1dmvqm\SkipApp.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 4d9fb3cb-7227-404f-a82b-deeffe63bd60 Faulting package full name: 1ee3f564-2cd0-4ef3-af35-da985b1d7f00_0.1.0.5293_x64__sddpyax1dmvqm Faulting package-relative application ID: App The remote makes a connecting sound when attached/detached from the PC. I do not see any updates on the app as if it is trying to connect. flirc20230120.txt.log

On the 1st post of the latest app, it says: "New Beta can be downloaded on the front page. Minor changes to help those with USB issues." I don't see it. Maybe I don't know which home page. Buried on page 7, I found this little gem: "When you are on the new user account, you should use the following build: 5276" For now, I'm going to start with this build.