Hi hmijail, as I tried to explain to you on GitHub: There is nothing strange about restoration failures of saved highlights for pages that change their content. In fact it's expected and I notify users in bold letters about it both on this addon page as well as on the Textmarker pages.
A restoration cannot be successful if:
1) The highlighted text is not on the page anymore (obviously) or
2) The "surrounding content" of the highlight has changed: As explained on GitHub, since DOM elements ceise to exist on page unload there is no way of saving a direct reference, which is why Textmarker has to rely on an indirect description of the highlight's location. This description holds information about the `nodeName` of the ancestor DOM elements as well as the position of those elements (i.e. 3rd child node of its parent element) and the corresp. text node's starting point of the selection. So a verbalized example description could be (a bit simplified):
"Starts at character 4 of the 3rd child node of a p-element, which is the first child of a div-element"
This is necessary, because a highlighted text could occur multiple times on a give page, so it wouldn't be sufficient on page revisit to just search for that text and highlight the first occurrence.

Update:
Latest version includes a shortcut for adding notes. By default this is Shift+N and disabled. Enable and customize on Settings>Shortcuts. Make sure the highlight to add the note to is being selected - i.e. by clicking it.

There are 3 easy ways to add notes to highlights:
1) via context menu (settings > shortcuts)
2) via button in Textmarker's sidebar -> just click a highlight first, then the button
3) under settings > markers you can equip any marker with automatic notes. Suggestion: just add a custom marker that will not only highlight but also automatically add a note in a color of choice ;)

for help please either contact the dev via e-mail (undflybir at gmx dot de) or open an issue on github (https://github.com/ufb/Textmarker/issues)

Why would you want to use Textmarker on pages that frequently change their text content? Doesn't make any sense to me. You can opt-out of automatic content script loading and decide yourself for each website to load Textmarker or not. Also, this skyrocketing CPU usage can't be reproduced - neither by me nor by users who help me testing. So, if you want to enjoy free open-source software with less bugs then helping the devs in supplying detailed bug reports would be more efficient than letting the world know about what'd be acceptable and what not. Cheers.