Viewer uses over 300mb per book

eSEB · 05-27-2021, 04:56 PM

Hello,

I recently updated to Calibre 5.17 from the 3.something I've used for a long time. I have had some issues with the viewer. I never had any issues before, so I can't say whether all of these "problems" are new. First, the viewer takes an inordinate amount time to load a book, and then, if it does load, it consumes over 300mb of RAM, even for a 150kb epub file. A second book take another 300+mb. And so on. Each book has four processes, the viewer plus three instances of C++ Application Development Framework. Second, and since I have plenty of RAM more important, the toolbar is gone. One can, for example, navigate through a book only one page at a time.

I'm using the 64bit version of Calibre for Windows 10.

Any help would be greatly appreciated.

eSEB

BetterRed · 05-27-2021, 05:24 PM

Quote:

Originally Posted by eSEB

. . .
Second, and since I have plenty of RAM more important, the toolbar is gone. One can, for example, navigate through a book only one page at a time.

Sorry, can't help with memory usage.

But show/Hide toolbar is the same as its always been, Ctrl+F11

BR

eSEB · 05-27-2021, 05:45 PM

Quote:

Originally Posted by BetterRed

Sorry, can't help with memory usage.

But show/Hide toolbar is the same as its always been, Ctrl+F11

BR

Ha! Thanks! All riled up about the RAM, I forgot to fn+ctrl as I went through the function keys. Thanks again.

eSEB

kovidgoyal · 05-27-2021, 08:49 PM

The RAM consumption comes from chromium, which the viewer uses since calibre 4.x. Complain to Google about chromium's memory footprint. As for slow first load, that is only first load of a book, subsequent loads will actually be faster than the viewer in 3.x (assuming your system doesnt have an underpowered GPU that causes chromium to take forever to initilize).

05-27-2021, 04:56 PM	#1
eSEB Junior Member Posts: 2 Karma: 10 Join Date: May 2021 Device: none	Viewer uses over 300mb per book Hello, I recently updated to Calibre 5.17 from the 3.something I've used for a long time. I have had some issues with the viewer. I never had any issues before, so I can't say whether all of these "problems" are new. First, the viewer takes an inordinate amount time to load a book, and then, if it does load, it consumes over 300mb of RAM, even for a 150kb epub file. A second book take another 300+mb. And so on. Each book has four processes, the viewer plus three instances of C++ Application Development Framework. Second, and since I have plenty of RAM more important, the toolbar is gone. One can, for example, navigate through a book only one page at a time. I'm using the 64bit version of Calibre for Windows 10. Any help would be greatly appreciated. eSEB

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
e-book viewer; preparing book for first read	fvdham	Library Management	7	05-15-2020 07:07 AM
wrong book cover in calibre book viewer	marp68	Library Management	17	08-10-2018 08:52 AM
Calibre E-book Viewer - Next E-book?	goldilocks	Calibre	2	03-11-2014 06:07 AM
E-Book Viewer as standalone viewer	Peter Swallow	Library Management	3	05-15-2011 12:06 PM
E-book viewer not properly remembering book position	sherman	Calibre	9	02-20-2010 05:12 PM

05-27-2021, 08:49 PM	#4
kovidgoyal creator of calibre Posts: 43,994 Karma: 22669822 Join Date: Oct 2006 Location: Mumbai, India Device: Various	The RAM consumption comes from chromium, which the viewer uses since calibre 4.x. Complain to Google about chromium's memory footprint. As for slow first load, that is only first load of a book, subsequent loads will actually be faster than the viewer in 3.x (assuming your system doesnt have an underpowered GPU that causes chromium to take forever to initilize).

Advert