Qt WebEngine Render process has crashed

ArtFlake · 07-09-2026, 05:58 PM

Calibre, version 9.11.0 (a previous version exhibited similar)
I'm getting this error on some fairly large books (nature guides with lots of photos). Also getting temporary stalls when scrolling fast in most books.

"ERROR: Render process crashed: The Qt WebEngine Render process has crashed. You should try restarting the viewer."

Restarting the viewer doesn't help.

Dell Precistion T1700 Desktop
Microsoft Windows 10 Pro Version; 10.0.19045 Build 19045 (x64)
Intel HD Graphics 4600 (on mainboard), latest drivers from Microsoft installed

No problems with VLC or other video players.

Web searches haven't turned up much sinces about 2020.
Any fixes?

I didn't see a sub-forum for "problems" or "bug reports"

JSWolf · 07-09-2026, 06:36 PM

Try safe mode and see what happens.

theducks · 07-09-2026, 06:45 PM

How Much RAM in that Dell? You may be pushing the Availability and it is swapping to disk on that book.
VLC seems to run on almost anything, any age.

kovidgoyal · 07-09-2026, 10:09 PM

Reboot in safe mode and see if the problem persists.

DiapDealer · 07-10-2026, 01:14 PM

Quote:

Originally Posted by ArtFlake

I'm getting this error on some fairly large books (nature guides with lots of photos). Also getting temporary stalls when scrolling fast in most books.

"ERROR: Render process crashed: The Qt WebEngine Render process has crashed. You should try restarting the viewer."

No problems with VLC or other video players.

I'm not quite following why "other video players" working would be relevant to a QtWebEngine browser crashing when rendering large books with "lots of photos."

ArtFlake · 07-14-2026, 06:24 PM

Assuming those recommending to boot into safe mode meant to boot Windows into safe mode (not simply re-starting Calibre), it did make a difference. I didn't get the crash, but I did get long (>2 minutes) pauses where control was lost.

Back in Windows regular mode, I monitored memory and GPU, and it is mainboard memory (16GB) that is maxing out when reading books with Calibre. GPU and GPU memory seemed to be coasting. As if I know what I'm talking about :-l

There are no other software problems on this machine that I'm aware of.

kovidgoyal · 07-14-2026, 10:54 PM

If it works in safe mode it means you have some software on your system interfering with calibre, typical culprits are security/antivirus and similar software.

JSWolf · Yesterday, 09:01 AM

Another thing to try is before you start calibre, close every program you have running. Then try calibre. That could help. The problem is that while 16GB may have been OK in the past, it's now gone to 32GB.

07-09-2026, 05:58 PM	#1
ArtFlake Junior Member Posts: 5 Karma: 10 Join Date: Feb 2020 Device: Nook	Qt WebEngine Render process has crashed Calibre, version 9.11.0 (a previous version exhibited similar) I'm getting this error on some fairly large books (nature guides with lots of photos). Also getting temporary stalls when scrolling fast in most books. "ERROR: Render process crashed: The Qt WebEngine Render process has crashed. You should try restarting the viewer." Restarting the viewer doesn't help. Dell Precistion T1700 Desktop Microsoft Windows 10 Pro Version; 10.0.19045 Build 19045 (x64) Intel HD Graphics 4600 (on mainboard), latest drivers from Microsoft installed No problems with VLC or other video players. Web searches haven't turned up much sinces about 2020. Any fixes? I didn't see a sub-forum for "problems" or "bug reports"

07-14-2026, 06:24 PM	#6
ArtFlake Junior Member Posts: 5 Karma: 10 Join Date: Feb 2020 Device: Nook	Safe Mode Results Assuming those recommending to boot into safe mode meant to boot Windows into safe mode (not simply re-starting Calibre), it did make a difference. I didn't get the crash, but I did get long (>2 minutes) pauses where control was lost. Back in Windows regular mode, I monitored memory and GPU, and it is mainboard memory (16GB) that is maxing out when reading books with Calibre. GPU and GPU memory seemed to be coasting. As if I know what I'm talking about :-l There are no other software problems on this machine that I'm aware of.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
calibre, version 6.22.0 ERROR: Render process crashed: The Qt WebEngine Render proces	georgezh9617	Viewer	2	07-24-2023 10:44 AM
Qt WebEngine Render process crash	DyckBook	Editor	1	05-25-2023 08:15 PM
Qt WebEngine Render	dunhill	Viewer	2	04-29-2022 04:29 PM
QT WebEngine Render process crashing	rjrizzuto	Calibre	25	03-18-2022 05:28 AM
IQ ua.pocketbook.bookinfo has crashed... and crashed...	Nightwish	PocketBook	6	02-13-2011 02:15 PM

07-09-2026, 06:36 PM	#2
JSWolf Resident Curmudgeon Posts: 84,150 Karma: 153695583 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Try safe mode and see what happens.

07-09-2026, 06:45 PM	#3
theducks Well trained by Cats Posts: 31,880 Karma: 64184592 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	How Much RAM in that Dell? You may be pushing the Availability and it is swapping to disk on that book. VLC seems to run on almost anything, any age.

07-09-2026, 10:09 PM	#4
kovidgoyal creator of calibre Posts: 46,374 Karma: 29630884 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Reboot in safe mode and see if the problem persists.

07-14-2026, 10:54 PM	#7
kovidgoyal creator of calibre Posts: 46,374 Karma: 29630884 Join Date: Oct 2006 Location: Mumbai, India Device: Various	If it works in safe mode it means you have some software on your system interfering with calibre, typical culprits are security/antivirus and similar software.

Yesterday, 09:01 AM	#8
JSWolf Resident Curmudgeon Posts: 84,150 Karma: 153695583 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Another thing to try is before you start calibre, close every program you have running. Then try calibre. That could help. The problem is that while 16GB may have been OK in the past, it's now gone to 32GB.