Suddenly 7.2.0 started crashing immediately on startup on my W7 machine since a few days.
The log file is empty.
Reinstalling did not help, but deleting (actually renaming so I kept the problematic one) the AppData\Local\YACReader dir did.

After some more diffing, it turns out that if I add POS=@Point(948 31) to the ini file the problem starts.
Removing the line solves it again (he adds a POS=@Point(0 0) himself).
SIZE=@Size(617 882)
(948 31) + (617 882) lies to be within my primary screen resolution (1680 x 1050), and he manages to draw the outline of the window before crashing so I do not immediately see the problem.
My screen setup is a bit special though:
-primary : 1680x1050
-others: 1200 x 1920 (portrait) and 1920 x 1080

Pressing the 'details' button of the the crash gives me:
Problem signature:
Problem Event Name: APPCRASH
Application Name: YACReader.exe
Application Version: 0.0.0.0
Application Timestamp: 5416d581
Fault Module Name: Qt5Gui.dll
Fault Module Version: 5.3.0.0
Fault Module Timestamp: 53750d35
Exception Code: c0000005
Exception Offset: 001fc801
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2067
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Thank you very much for reporting the bug. Tomorrow I will try to replicate it in a multi-screen setup.

Any luck reproducing the issue ?
I am now running into the crash again, but resetting the ini file does not work this time.
So actually I am not sure it is the same error, though it looks completely similar:
Problem signature:
Problem Event Name: APPCRASH
Application Name: YACReader.exe
Application Version: 0.0.0.0
Application Timestamp: 5416d581
Fault Module Name: Qt5Gui.dll
Fault Module Version: 5.3.0.0
Fault Module Timestamp: 53750d35
Exception Code: c0000005
Exception Offset: 001fc801
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2067
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Not sure what could be different than last time, i am thinking maybe the 1920x1080 monitor (actually a tv) being turned off (but switching it on/off now does not seem to make a difference, maybe i need to reboot).

If there is anything I can try to get more logging about what exactly he is doing (a verbose option?) let me now.

Owkee, now things get strange.

I have 2 explorers open (actually 2xExplorer, a good old 32 bit dual pane explorer, maybe that plays a role too).
One is on the primary 1680x1050 screen, the other is on a secondary 1200 x 1920 screen.

If I double click on a comic in the explorer on the primary screen, yacr opens on the primary screen and works just fine.

If I double click on a comic in the explorer on the secondary screen, yacr still opens on the primary screen but crashes.

( I don't remember if I by pure coincidence did this as well when I reported the original error, and I am still not 100% believing what I see here ;p ).

Thank you for the detailed description of the issue.

I have connected a second screen to my setup, primary screen 2560x1440 and a secondary screen 1920x1080. I have also tried with the secondary screen in portrait mode and everything is working fine for me.

I hate when this things happen, because It's really difficult to solve a bug that I can't replicate.

What graphic card do you have? Could you get the latest graphic drivers for your card?

Thank you again for your help.

This could very well be a Qt bug.

Beamer, since Luis has troubles replecating the issue, would you feel comfortable with running YACReader in a debugger? This way we could investigate where exactly in the code the crash is triggered.

I've never debugged on a recent version of Windows, but I guess Luis could provide you with the stuff necessary (Debug build of YAC, his debugger of choice, guidance...). It may take the willingness to do a little learning on how to do this, but it's not rocket science and it will help a lot in determining the source of your issues.

Hi,

Graphic card is an Asus EAH6950 DCII 2Gb.

If I go into the device manager and check display adapters, I get AMD Radeon HD 6900 series with driver version 8.961.0.0 , dated 8/04/2012.
So that is pretty old, I don't game much anymore these days so not much incentive to keep up with the latest drivers, and if it ain't broke I don't try to fix it .
The asus site does not list anything newer for my card, but I am downloading drivers from AMD directly now, I will report back when that's done.

If you want me to try something in the debugger that should not be a problem (embedded SW programmer by trade, so usually I am working a bit more lower level but I should be able to follow instructions )


EDIT: Ok, after updating to 14.501.1003.0, things seem to work now. I will keep my fingers crossed that this is permanent. Thanks a lot for the support !

Great. Let me know if you any other issues.