Thread: suggestion - kepubify: optimize spans for compatibility with text-modifying plugins
View Single Post
Old 05-16-2025, 06:10 AM   #5
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,856
Karma: 146918083
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by DNSB View Post
Reading his original message, what he wants is for Kovid to add special case logic to hand the mass of <b>....</b> that are added to the code. He claims that those extra spans added around the <b>s are causing out of memory errors and slow chapter turning. I did test his plugin with an ~1.4M word omnibus and could see little difference in performance when I send any of the 4 variants I generated to my Sage. According to running free -m from NickelMenu, none of the 4 variants caused even close to an out of memory issue.
I would expect a performance hit having to render all of those bolds. But I would not expect an out of memory error.

My question is, does the OP have anything running such as Nickelclock?
JSWolf is offline   Reply With Quote