Crashing and other problems in version 1.4.0.0 or newer

[Ninja_Gah]

We've received reports of people experiencing crashes in 1.4.0.0 or newer.

The first thing we'd ask you to do is to reinstall the app. Otherwise please see below see how you can help us debug.

Crashing could be caused by a few problems:
1. Upgrading from an old version of app - reinstall should fix
2. Corrupted settings - reinstall should fix
3. Incompatibility with OpenCV - please send us the archive images that you are trying to open

Regarding 1 & 2
1.4.0.0 uses a new modular settings systems. When you upgrade to 1.4.0.0 or later it attempts to upgrade old settings to the new settings. We did our best to try and catch all corner cases but it seems like for some people the upgrade will crash the app, including a reinstall for some. This undefined behavior makes it extremely difficult to debug. If you are crashing on launch on a fresh please make a post down below with your system spec.

Regarding 3
OpenCV makes it possible for us to do fancy things like border removal. We can't guarantee it's bug free as it is a third party library. Luckily it's open source and if there is an issue we can fix it. Our internal testing shows it works fine with all our limited archives and image collection but some are reporting crashes. If you experience crashes when opening an image/archieve, missing pages, strange coloring, please pm me a link of the archive you are using and we can attempt to debug this issue.

[Tooya]

Hey, I have this problem on my tablet and no solution is working. When I try to run Comics++ it just shuts down after few seconds of loading, if I run it by opening any comic archive the same happens with addition of "remote procedure call failed" error.
I already tried:
-reinstalling
-reinstalling after manualy cleaning registry of every entry related to Comics++
-updating windows and then reinstalling
-creating new user and installing your app there
-every sollution to "remote procedure call failed" error that I could find in google (and here http://comicsplusplus.com/showthread.php?tid=73)
I even installed Comics++ on my desktop, where it was never installed previously (or any other app not built in into win10)
Here are logs from windows event wiever and my system information (unluckily both only from my desktop as I keep tablet in my work)

Code:

OS Name Microsoft Windows 10 Pro
Version 10.0.15063 Build 15063
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name TOOYA
System Manufacturer MSI
System Model MS-7816
System Type x64-based PC
System SKU To be filled by O.E.M.
Processor Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz, 3601 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. V1.7, 20.02.2014
SMBIOS Version 2.8
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer MSI
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale Polska
Hardware Abstraction Layer Version = "10.0.15063.502"
User Name Tooya\Jakub
Time Zone Central European Standard Time
Installed Physical Memory (RAM) 8,00 GB
Total Physical Memory 7,94 GB
Available Physical Memory 4,07 GB
Total Virtual Memory 9,19 GB
Available Virtual Memory 4,56 GB
Page File Space 1,25 GB
Page File C:\pagefile.sys
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Code:

Log Name:      Application
Source:        Application Error
Date:          18.11.2017 15:35:24
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Tooya
Description:
Faulting application name: Comics++.exe, version: 0.0.0.0, time stamp: 0x5a078084
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.15063.674, time stamp: 0xaf452875
Exception code: 0xc000027b
Fault offset: 0x0000000000443b5f
Faulting process id: 0x17a4
Faulting application start time: 0x01d3607a7767100f
Faulting application path: C:\Program Files\WindowsApps\48694Comics.Comics_1.4.3.0_x64__tevn358vk4h6m\Comics++.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 4e244654-6d80-48d2-abf1-065e24f85f8f
Faulting package full name: 48694Comics.Comics_1.4.3.0_x64__tevn358vk4h6m
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
   <Provider Name="Application Error" />
   <EventID Qualifiers="0">1000</EventID>
   <Level>2</Level>
   <Task>100</Task>
   <Keywords>0x80000000000000</Keywords>
   <TimeCreated SystemTime="2017-11-18T14:35:24.707393100Z" />
   <EventRecordID>25777</EventRecordID>
   <Channel>Application</Channel>
   <Computer>Tooya</Computer>
   <Security />
 </System>
 <EventData>
   <Data>Comics++.exe</Data>
   <Data>0.0.0.0</Data>
   <Data>5a078084</Data>
   <Data>Windows.UI.Xaml.dll</Data>
   <Data>10.0.15063.674</Data>
   <Data>af452875</Data>
   <Data>c000027b</Data>
   <Data>0000000000443b5f</Data>
   <Data>17a4</Data>
   <Data>01d3607a7767100f</Data>
   <Data>C:\Program Files\WindowsApps\48694Comics.Comics_1.4.3.0_x64__tevn358vk4h6m\Comics++.exe</Data>
   <Data>C:\Windows\System32\Windows.UI.Xaml.dll</Data>
   <Data>4e244654-6d80-48d2-abf1-065e24f85f8f</Data>
   <Data>48694Comics.Comics_1.4.3.0_x64__tevn358vk4h6m</Data>
   <Data>App</Data>
 </EventData>
</Event>

Code:

Log Name:      Application
Source:        Windows Error Reporting
Date:          18.11.2017 15:35:28
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Tooya
Description:
Fault bucket 1655578245712778034, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: 48694Comics.Comics_1.4.3.0_x64__tevn358vk4h6m
P2: praid:App
P3: 0.0.0.0
P4: 5a078084
P5: combase.dll
P6: 10.0.15063.608
P7: b66dc19d
P8: 802b000a
P9: 0000000000021bd9
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5FD.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD84F.tmp.WERInternalMetadata.xm​l
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD85E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD86F.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_48694Comics.Comi_d38​49f435452935efad45e1b418043bc9a7bedf4_48bf8bc4_272ae128

Analysis symbol:
Rechecking for solution: 0
Report Id: 4e244654-6d80-48d2-abf1-065e24f85f8f
Report Status: 268435456
Hashed bucket: 9a6f10b8419832b576f9cba491931332
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
   <Provider Name="Windows Error Reporting" />
   <EventID Qualifiers="0">1001</EventID>
   <Level>4</Level>
   <Task>0</Task>
   <Keywords>0x80000000000000</Keywords>
   <TimeCreated SystemTime="2017-11-18T14:35:28.444648000Z" />
   <EventRecordID>25778</EventRecordID>
   <Channel>Application</Channel>
   <Computer>Tooya</Computer>
   <Security />
 </System>
 <EventData>
   <Data>1655578245712778034</Data>
   <Data>5</Data>
   <Data>MoAppCrash</Data>
   <Data>Not available</Data>
   <Data>0</Data>
   <Data>48694Comics.Comics_1.4.3.0_x64__tevn358vk4h6m</Data>
   <Data>praid:App</Data>
   <Data>0.0.0.0</Data>
   <Data>5a078084</Data>
   <Data>combase.dll</Data>
   <Data>10.0.15063.608</Data>
   <Data>b66dc19d</Data>
   <Data>802b000a</Data>
   <Data>0000000000021bd9</Data>
   <Data>
   </Data>
   <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5FD.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD84F.tmp.WERInternalMetadata.xm​l
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD85E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD86F.tmp.txt</Data>
   <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_48694Comics.Comi_​d3849f435452935efad45e1b418043bc9a7bedf4_48bf8bc4_272ae128</Data>
   <Data>
   </Data>
   <Data>0</Data>
   <Data>4e244654-6d80-48d2-abf1-065e24f85f8f</Data>
   <Data>268435456</Data>
   <Data>9a6f10b8419832b576f9cba491931332</Data>
 </EventData>
</Event>

Code:

Log Name:      Application
Source:        Microsoft-Windows-Immersive-Shell
Date:          18.11.2017 15:35:28
Event ID:      5973
Task Category: (5973)
Level:         Error
Keywords:      
User:          TOOYA\Jakub
Computer:      Tooya
Description:
Activation of app 48694Comics.Comics_tevn358vk4h6m!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
   <Provider Name="Microsoft-Windows-Immersive-Shell" Guid="{315A8872-923E-4EA2-9889-33CD4754BF64}" />
   <EventID>5973</EventID>
   <Version>0</Version>
   <Level>2</Level>
   <Task>5973</Task>
   <Opcode>0</Opcode>
   <Keywords>0x2000000000000000</Keywords>
   <TimeCreated SystemTime="2017-11-18T14:35:28.463179600Z" />
   <EventRecordID>25779</EventRecordID>
   <Correlation />
   <Execution ProcessID="9420" ThreadID="9148" />
   <Channel>Application</Channel>
   <Computer>Tooya</Computer>
   <Security UserID="S-1-5-21-2920716571-1592115977-651716476-1001" />
 </System>
 <EventData>
   <Data Name="AppId">48694Comics.Comics_tevn358vk4h6m!App</Data>
   <Data Name="ErrorCode">-2147023170</Data>
 </EventData>
</Event>

[Ninja_Gah]

Thanks for the report!

I believe we found the issue. It is related to opening the the app externally through Windows explorer rather than using the in app file browser. There were settings problems that broke opening files externally. In the meantime, you should be able to use the in-app file browser to open files.

We'll be pushing an update today that fixes this issue so it'll be up on the store in a few days.

However if this is not your issue please continue to report. Thanks!

[Tooya]

Thanks for the quick reply, I'll try again after the update but as for using the in-app file browser, as I wrote previously, I can't run the app itself, it opens and, after a second or two, shuts down without giving any error and it's both on my tablet, where it was used before so it may be trying to open last used comic, and desktop where it's straight after the first installation so I haven't opened any comic with it yet or even set a path to my comics.On both devices I use menu start to run the app, I only used windows explorer to check if this changes anything after Comics++ stopped working normally.

[Ninja_Gah]

I see. Yes if you opened files externally without using the in app browser you may be stuck in a crash loop.

To fix this temporarily until next release is deployed:
1. Reinstall the app
2. Launch app directly without opening a book
3. Use the in app file browser to open a book

Afterwards all operations should be normal, including opening files externally. The main issue was there was a setting that didn't get upgraded correctly due to activated books which sort of snowballs the issue. As long as you didn't first launch app by opening a book externally after upgrade then it would function normally.

Hopefully our latest version fixes this issue...

[Tooya]

Thanks for trying to help but again, I only tried to open file externally when the app stopped working correctly, and thats only on my tablet, on the desktop I never tried to open any archive just the app directly after completely fresh install on a machine that C++ app was never installed previously.
Well it's not urgent, maybe I'll just wait for the update and let You know if this fixes my problems

[Ninja_Gah]

Sorry just to clarify, are you saying a fresh install on your desktop computer still crashes on launch (not activated by file)?

[Tooya]

yes, I installed Comics++ on my desktop after it stopped working on my tablet just to try whether it was working or not, it was never used to open any actual comic archive because it was crashing from the first try to open the app alone.

[Ninja_Gah]

Ok thanks that's interesting as it shouldn't have passed certification if that was case. This means that it there are some hardware difference causing variation in behavior.

Anyways I believe the fixes we pushed should address that issue as well. My guess is that we tried to initialize settings before all of the UI components finished loading. On difference system specs there can be a race condition, so if the UI hasn't finished loading before the settings kick in it may cause a crash. It now waits until UI is completely loaded then applies the settings.

I just checked the publishing status it should be up on the store soon, if not already. Please keep me updated if this build fixes the issues. Thank you so much!

[Tooya]

Hey again, I've checked new version on both tablet and desktop and unluckily it still shuts down before it even finishes loading.