Fail Fast Exception error

[varis1]

I went back to 4.2 -> there is no error message
reinstalled 4.10.1 -> same problem

another problem is marking more books with shift+mouse click doesn't work propper. in other programms -> no problem

[Horus68]

This must be one of those days.

The problem is back so now I went for a full test and I think this must be a Calibre issue.
Why? It can be replicated with specific Calibre portable versions. Lets go for details (including debug logs)!


1- When it happens?
Always after closing the Calibre reader.
There is an alert window for "calibre-parallel.exe"
Picture attached (My windows system its in Portuguese but the image reads like the initial user posted:

Calibre: calibre-parallel.exe - Fail Fast Exception
A fail fast exception occured. Exception handlers will not be invoked and the process will be terminated immediately.

2- What OS / Calibre version?
Win10 Pro 32 bits, Windows Defender

Error shows when using
- Calibre full - 4.10.1
- Calibre Portable 4.10.0 and 4.10.1

No error when using
- Calibre Portable 3.4.8 and 4.9.1

Note 1: Both (4) Calibre Portable was done using the 32 bits versions from Calibre download site.
Note 2: the 4 Calibre Portable installation was done at the same date and same directory level, no spaces or special letters, as in:
D:\SoftwProdutos\Calibre\348
D:\SoftwProdutos\Calibre\491
D:\SoftwProdutos\Calibre\4101
D:\SoftwProdutos\Calibre\4100

3- Book used for testing?
The ePub "Quick Start Guide" (available in each Calibre Portable installation library folder)
Book opened from menu button. The second time it was also reloaded (right click button in Reader)

4- Antivirus? Windows Defender off or on = Same result
- Created a folder exclusion. Same result
- No "Folder controlled access"


5- Windows Safe Mode? Tested with Windows Safe Mode (no internet connection).
Result: same error for all Calibre versions

6- Calibre Debug mode? Tested with Calibre Debug mode. Same error!

I used a bat file from https://www.mobileread.com/forums/sh...63&postcount=2
The command is

calibre-debug -g 1>> log.txt 2>&1

7- Log output
Log file is from the Calibre 4.10.1 full instance with the CalibrePortable 4.10.1 default Library (I don't know how to create a debug log directly from the Calibre Portable)

calibre 4.10.1  embedded-python: True is64bit: False
Windows-10-10.0.16299-SP0 Windows ('32bit', 'WindowsPE')
('Windows', '10', '10.0.16299')
Python 2.7.16+
Windows: ('10', '10.0.16299', 'SP0', u'Multiprocessor Free')
Interface language: pt
Successfully initialized third party plugins: Generate Cover (1, 5, 22) && Barnes & Noble (1, 2, 15) && Quality Check (1, 9, 11) && Embed Comic Metadata (1, 4, 0) && Save Virtual Libraries To Column GUI (2, 2, 1) && Find Duplicates (1, 6, 3) && Goodreads (1, 4, 0) && Job Spy (1, 0, 172) && EpubCheck (0, 2, 2) && Kobo Books (1, 8, 0) && Count Pages (1, 9, 0) && Goodreads Sync (1, 14, 2) && Fantastic Fiction (1, 3, 0) && FictionDB (1, 2, 0)
Turning on automatic hidpi scaling
devicePixelRatio: 1.0
logicalDpi: 96.0 x 96.0
physicalDpi: 95.8113948919 x 95.9160839161
Using calibre Qt style: True
[0.00] Starting up...
[0.01] Showing splash screen...
[0.86] splash screen shown
[0.86] Initializing db...
[0.86] db initialized
[0.86] Constructing main UI...
DEBUG:    0.0 Goodreads Sync::dialogs.py - loading translations
DEBUG:    0.0 GoodreadsSync::action.py - loading translations
Job Spy has begun initialization...
Calibre, and hence Job Spy, was gracefully shut down last time?  True
Last time daemon started:  never
Last time daemon failed:  never
Total daemon starts inception_to_date:  0
Total daemon failures inception-to-date:  0
libpng warning: iCCP: known incorrect sRGB profile
Job Spy has finished initialization...
DEBUG:    1.8 HttpHelper::__init__: proxy=None
[3.05] main UI initialized...
[3.05] Hiding splash screen
[3.19] splash screen hidden
[3.20] Started up in 3.20 seconds with 1 books
Worker Launch took: 0.236999988556

- Log file from the Calibre 4.10.1 full instance with a small sample library

calibre 4.10.1  embedded-python: True is64bit: False
Windows-10-10.0.16299-SP0 Windows ('32bit', 'WindowsPE')
('Windows', '10', '10.0.16299')
Python 2.7.16+
Windows: ('10', '10.0.16299', 'SP0', u'Multiprocessor Free')
Interface language: pt
Successfully initialized third party plugins: Barnes & Noble (1, 2, 15) && Count Pages (1, 9, 0) && Job Spy (1, 0, 172) && FictionDB (1, 2, 0) && Kobo Books (1, 8, 0) && Generate Cover (1, 5, 22) && Embed Comic Metadata (1, 4, 0) && Save Virtual Libraries To Column GUI (2, 2, 1) && Quality Check (1, 9, 11) && EpubCheck (0, 2, 2) && Goodreads Sync (1, 14, 2) && Fantastic Fiction (1, 3, 0) && Find Duplicates (1, 6, 3) && Goodreads (1, 4, 0)
Turning on automatic hidpi scaling
devicePixelRatio: 1.0
logicalDpi: 96.0 x 96.0
physicalDpi: 95.8113948919 x 95.9160839161
Using calibre Qt style: True
[0.00] Starting up...
[0.00] Showing splash screen...
[0.86] splash screen shown
[0.86] Initializing db...
[0.88] db initialized
[0.88] Constructing main UI...
DEBUG:    0.0 Goodreads Sync::dialogs.py - loading translations
DEBUG:    0.0 GoodreadsSync::action.py - loading translations
Job Spy has begun initialization...
Calibre, and hence Job Spy, was gracefully shut down last time?  False
Last time daemon started:  never
Last time daemon failed:  never
Total daemon starts inception_to_date:  0
Total daemon failures inception-to-date:  0
libpng warning: iCCP: known incorrect sRGB profile
Job Spy has finished initialization...
DEBUG:    2.0 HttpHelper::__init__: proxy=None
[3.30] main UI initialized...
[3.31] Hiding splash screen
[3.58] splash screen hidden
[3.58] Started up in 3.58 seconds with 25 books
Worker Launch took: 0.264999866486
QObject::~QObject: Timers cannot be stopped from another thread
^C

[BetterRed]

@Horus68 - that (10.0.16299) is a rather old version of Windows 10, according to Microsoft it's 1709, is it up to date?

Perhaps other Fast Fail reporters could tell us what version of Windows 10 they are using.

Curious: why have you not upgraded to a later version?

BR

[Horus68]

Originally Posted by BetterRed

Curious: why have you not upgraded to a later version?
BR

True. For some time my system has a failure when upgrading to latest windows build requiring a roll back (I need to have the autoupdate paused, and each month a roll back after a major update)

I also had to use the 32 bit version (even if the machine has a 64 bits I5 processor) because of some software required for my work at home.
Next August i plan to install a fresh machine with Windows 64 bits as I will move to a different job position that don't require actual old software anymore.

[BetterRed]

Originally Posted by Horus68

True. For some time my system has a failure when upgrading to latest windows build requiring a roll back (I need to have the autoupdate paused, and each month a roll back after a major update)

I also had to use the 32 bit version (even if the machine has a 64 bits I5 processor) because of some software required for my work at home.
Next August i plan to install a fresh machine with Windows 64 bits as I will move to a different job position that don't require actual old software anymore.

- aaah, the old problem of work getting in the way of life.

BR

[JSWolf]

Originally Posted by varis1

after update to 4.10.1 the error takes place when closing editor and reader. exclusiv with calibre.

win 1809 pro up to date

The error is most likely due to the fact that you are running a very old version of Windows 10. Microsoft is ending support for 1809. Update to the latest version of Windows 10 and then come back and say if it works or not.

I have Windows Home and Pro 1903 64-bit and Calibre runs without any problem.

[JSWolf]

Originally Posted by BetterRed

@Horus68 - that (10.0.16299) is a rather old version of Windows 10, according to Microsoft it's 1709, is it up to date?

Perhaps other Fast Fail reporters could tell us what version of Windows 10 they are using.

Curious: why have you not upgraded to a later version?

BR

1909 is the current version of Windows 10. I'm using 1903 and Calibre is working perfectly well here on multiple computers. 1709 is 3 or 4 Windows versions behind.

[JSWolf]

Originally Posted by Horus68

True. For some time my system has a failure when upgrading to latest windows build requiring a roll back (I need to have the autoupdate paused, and each month a roll back after a major update)

I also had to use the 32 bit version (even if the machine has a 64 bits I5 processor) because of some software required for my work at home.
Next August i plan to install a fresh machine with Windows 64 bits as I will move to a different job position that don't require actual old software anymore.

What I would have done is told work that I cannot run this old software and if they want me to run it, they will have to supply the computer. There is no way I would cripple my computer because of work.

[Horus68]

Originally Posted by JSWolf

What I would have done is told work that I cannot run this old software and if they want me to run it, they will have to supply the computer. There is no way I would cripple my computer because of work.

Sometimes that's life! Just some months to the end!

[JSWolf]

Originally Posted by Horus68

Sometimes that's life! Just some months to the end!

It's your computer paid for with your money and you should have the right to run the current version of Windows 10 64-bit. I would just say that I can't do it on my computer and if you need me to run this software at home, you'll need to supply me with a computer that I can run it on. You are unable to run the software you want to run on your computer because of work. That's not fair to you.

[PeterT]

Personally I'm more inclined to link it video driver issues and not Windows.

[BetterRed]

Originally Posted by BetterRed

@Horus68 - that (10.0.16299) is a rather old version of Windows 10, according to Microsoft it's 1709, is it up to date?

Perhaps other Fast Fail reporters could tell us what version of Windows 10 they are using.

Curious: why have you not upgraded to a later version?

BR

Originally Posted by JSWolf

1909 is the current version of Windows 10.

Do you really think I don't know that.

Originally Posted by JSWolf

I'm using 1903 and Calibre is working perfectly well here on multiple computers.

I know, you tell us 10 times a day

So Jon, why are you running an old version of Windows on multiple computers. I assume you know that 1909 is probably already on your 1903 systems, if you run the appropriate enablement package then within a couple of minutes you'll have 1909.

FTR - I'm running version 1909 build 18363.657.

BR

[DNSB]

Originally Posted by BetterRed

FTR - I'm running version 1909 build 18363.657.

Why are y'all running such an old version? Version 2004 build 19564.1005 is where it's at.

[kovidgoyal]

It almost certainly an issue between Qt WebEngine 5.14 and the video drivers on the problem machines. Thankfully it doesn't affect functionality.

[varis1]

Originally Posted by JSWolf

The error is most likely due to the fact that you are running a very old version of Windows 10. Microsoft is ending support for 1809. Update to the latest version of Windows 10 and then come back and say if it works or not.

I have Windows Home and Pro 1903 64-bit and Calibre runs without any problem.

The problem is not my windows 1809, which is in imo fully supported and not "very" old and never change a running system. the problem is calibre 4.10.1. I went back to 4.9.1 and there is no problem.