Here are theĭetails of the SSBs I have created with Epichrome that run all the time. Hey! Sorry it's taken me so long to get back to you. Sorry it's a lot of info, but I won't be able to diagnose or fix the problem if I can't recreate it on my system.
![epichrome multiple tabs epichrome multiple tabs](https://www.minitool.com/images/uploads/news/2019/03/display-your-last-active-app-window/display-your-last-active-app-window-thumbnail.png)
I originally developed Epichrome on 10.9, and can't think of any reason why it would exhibit this behavior.
![epichrome multiple tabs epichrome multiple tabs](https://cdn.ghacks.net/wp-content/uploads/2008/08/firefox_tabs_multiple_rows.jpg)
I wonder if it's possibly to do with being on Mavericks vs. Looks like you're up-to-date with Chrome. I hope that last paragraph makes sense! It's a bit hard for me to accurately explain without knowing all the technical terms that are supposed to be used. Then, if I quit the SSB that is getting affected, then the behavior will effect one of the others that's running, and even if I re-open the SSB that was being affected previously, the behavior will still be tied to the other SSB. The behavior seems to get locked to one of the running SSBs, and even if that SSB is furthest in the back, it will be the one that gets brought to the front. But I don't get any error, warning, etc.Īlso, I just noticed, the SSB that gets brought to the front when I try to open Chrome is not necessarily the SSB that's closest to the front, as I incorrectly stated before.
![epichrome multiple tabs epichrome multiple tabs](https://wiki.scn.sap.com/wiki/download/attachments/135987485/contract_tab.png)
when the behavior occurs, other than one of the running SSBs being brought up to the front of the running apps. When you say "the summary dialog for an SSB that exhibits this behavior", are you talking about the console log or something else? Nothing pops up, etc. Also, all the SSBs I have running have auto-updated themselves to the latest version of Chrome. Hey just updated to the latest Chrome (.157 (64-bit)) and the issue stills exists.