[RH2020.5.71] Search Freezes On Random Search Terms (responsive HTML5 output)

I'm not sure I would mark that as a correct answer as it doesn't solve the problem. Of course, the problem Adobe are going to have is the same as yours, replicating it. I hope they can.

If you can consider a frameless output, a lot of work has been done on search there. I can't say it will fix the issue but maybe worth a try if it is an option.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Given the nature of this bug and the fact that it happens across all browsers and that other people have posted to say they have a similar issue, I've gone ahead and filed a bug with Adobe. 

https://tracker.adobe.com/#/view/RH-10017

Please upvote it if you are having the same issue. 🙂

Yes! I've seen this behavior also and always concluded it was my system acting up. Now that I know it's happening to others, I'll pay closer attention and try to figure out some kind of pattern.

Thanks for posting about this!

I have noticed this with RH 2019 HTML5 Azure. It hasn't happened frequently enough for me to make a fuss about it, but every now and then something strange happens during a search which is solved by a page refresh and searching again. It's too infrequent to pinpoint it, but indeed page freezes (at several stages of loading) might describe it best. In my experience it happens more when using it locally (especially when using index.htm files over the network) than when we've uploaded it to our web server and opening the help using an URL. YMMV. 

Probably is some kind of javascript blip if the connection is interrupted during execution or something like that.

Commonly known as a bar steward!

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Thank you Peter for the swift reply. We are currently testing local builds just now, but given the seemingly random nature of this issue, we could test 2000 search terms and find nothing or we could serach 20 and find the issue 5 times! At the moment, it hasn't happened, but that's not to say it won't... I didn't consider testing from another network location though... so I'll give that a go too and see what happens.

Once I've given these options a thorough testing to see if there is any difference or reproduction, I'll contact support as you suggest.

Honestly, this is the worst kind of bug... 😞

Thanks!!!!

I don't think it has been an issue.

I note this is when it is on a server so do you get the same issue if you run the output locally? Are you able to generate to another folder on the network to see if it still occurs?

Beyond that, unless someone else has ideas or has seen the problem, I can only suggest Support to see if they are aware of an issue. See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. The email link tcssup@adobe.com is recommended as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information