It's definitely a memory leak from the conversation API. It seems to keep track of browser state and to limit computation on their end based on the 'active' tab.