[GH-ISSUE #93] Unresponsive after back in focus #66

New issue

Closed

opened 2026-03-03 16:04:08 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 16:04:08 +03:00

Owner

Originally created by @mefjush on GitHub (Feb 25, 2017).
Original GitHub issue: https://github.com/mthenw/frontail/issues/93

How to reproduce:

Lose the window focus
Push a large number of lines to the log file (1000?)
Focus the window again
The page is unresponsive for quite a while (not able to scroll, select/deselect lines, etc)
(Tested on Chrome 56.0.2924.87 on Mac OS)

It looks like Tinycon needs a lot of cpu time to execute setBubble (and it's invoked for each new line).

As a temporary bypass I've used this hack:

Tinycon.innerSetBubble = Tinycon.setBubble;
var faviconUpdateTimer = null;
var faviconN = 0;
Tinycon.setBubble = function(n) {
  faviconN = n;
  if (!faviconUpdateTimer) {
    faviconUpdateTimer = setTimeout(function() {
      faviconUpdateTimer = null;
      Tinycon.innerSetBubble(faviconN);
    }, 1000);
  }
};

Originally created by @mefjush on GitHub (Feb 25, 2017). Original GitHub issue: https://github.com/mthenw/frontail/issues/93 How to reproduce: 1. Lose the window focus 2. Push a large number of lines to the log file (1000?) 3. Focus the window again 4. The page is unresponsive for quite a while (not able to scroll, select/deselect lines, etc) (Tested on Chrome 56.0.2924.87 on Mac OS) It looks like Tinycon needs a lot of cpu time to execute setBubble (and it's invoked for each new line). As a temporary bypass I've used this hack: ``` Tinycon.innerSetBubble = Tinycon.setBubble; var faviconUpdateTimer = null; var faviconN = 0; Tinycon.setBubble = function(n) { faviconN = n; if (!faviconUpdateTimer) { faviconUpdateTimer = setTimeout(function() { faviconUpdateTimer = null; Tinycon.innerSetBubble(faviconN); }, 1000); } }; ```

kerem closed this issue

2026-03-03 16:04:09 +03:00

kerem commented

2026-03-03 16:04:09 +03:00

Author

Owner

@mthenw commented on GitHub (Feb 27, 2017):

Thanks for info. I will looks into it.

@mthenw commented on GitHub (Feb 27, 2017): Thanks for info. I will looks into it.

kerem commented

2026-03-03 16:04:10 +03:00

Author

Owner

@mthenw commented on GitHub (Feb 27, 2017):

Hey,

I've just publish v4.0.2. Please check and let me know if this issue still occurs.

@mthenw commented on GitHub (Feb 27, 2017): Hey, I've just publish v4.0.2. Please check and let me know if this issue still occurs.

kerem commented

2026-03-03 16:04:10 +03:00

Author

Owner

@mefjush commented on GitHub (Feb 28, 2017):

Yup. That solves the problem. Thanks.

@mefjush commented on GitHub (Feb 28, 2017): Yup. That solves the problem. Thanks.