I've attached an .rtf with all the regexes I run, in order (and notes to myself about what each regex is supposed to do). It's quite tedious, lol, but I'd rather fix things up front than be annoyed by problems in the middle of reading. The memory leak shows up most quickly in non-fiction books with lots of formatting, like footnotes, index entries, bibliographies with a href links, etc. The more complicated the better.
Quote:
Originally Posted by KevinH
It could be a regex related search and replace that has a memory leak we simply have not touched on. For a leak to show up in Valgrind or macOS "leaks tool" you have to actually exercise the problem code to detect a leak.
So it would really help us if you could please post a sample epub and a list of regex expressions you run typically and the order. That way we can try the exact samething you are doing in a leak detector to see if memory really is leaking. Please try to include an exact set of steps that seems to use the most memory.
If you prefer, you can pm DiapDealer and KevinH here with the link to the epub and list of regexes.
I really would like to get this tracked down and fixed.
Thanks,
KevinH
|