Performance differences between SupportTextSelection(true) and false in the image mode

GroupDocs.Viewer Product Family
21

Hello, thanks for your recomendations.


"We are sorry to hear that you have this issue. Please tell us a bit more about the crashing of the browser? Which browser is crashing while displaying the “MH.pdf” document? Are there any messages? Can you reproduce the crash using some another browser?"
  • The browser is crashing is Chrome (see attach via email).
  • I try with Firefox, it works better but sometimes it takes some seconds to respond. (See message screenshot in the attach).
I follow your steps, but it still no working ok.

If I change GenerateImages(…) to GenerateHtml(…) may be it works better? Which differences exists between those methods?

Thank you.
22

Hello Alexis,

Sorry for the long delay.

1. First of all, we released a new version of the GroupDocs.Viewer 2.7. A lot of bugs were fixed along with a lot of new features were introduced, including those which was requested by you, for example, accent-insensitive search.

2. We must admit that the opening and rendering of the “730E SM A30260-A30298 ING CEAM013101.pdf” file requires tremendous amount of time even if using a cache. We were able to reproduce the Google Chrome warning, saying that the page doesn’t respond - this occurs while rendering of the document, when GroupDocs.Viewer doesn’t send the responses at time.

3. About GenerateImages/GenerateHtml. First method generates image-based cache for image-based rendering engine. Second method generates HTML-based cache for HTML-based rendering engine. HTML-based mode usually works faster, when document contains a lot of textual information, and a total size of the cache is a much, much lesser. But in some cases using this mode the document may be rendered incorrectly. You should try to open your documents using HTML-based mode and to make a choice, if the rendering quality is acceptable for you or not.

Thanks and sorry for the delay.

23

Hello Alexis,

We want to additionally explain the situation with Google Chrome warning, saying that the page doesn’t respond. We know about this issue - it occurs when GroupDocs.Viewer performs a rendering (converting to the HTML-compatible form) of a document. If the document is big, during the rendering GroupDocs.Viewer doesn’t respond on the client-side requests, so the browser “thinks” that the web-page is frozen.

Now our developers are investigating this problem, thinking about approaches and techniques, which can solve this issue.