Seems when you put Opera in full screen mode and then try to then take it out of full screen mode and then back again, the full screen mode button and the minimize buttons are greyed out. This is on the Final release of Catalina.

Very sad that I had to transition over to using Brave as my work browser. Seeing as I've been using Opera since it was based on Presto -1995 was a good year for Opera. Lets see if this issue gets resolved.

Oh wow a response. Seems thats the only way people respond.

It's still happening. F***ing ridiculous.

@leocg

Hope this is helpful.

@leocg That is with a clean Opera profile, I removed it, reinstalled it then tested again. As for another Chromium based browser I've tested it on Brave and it's not happening there.

Completely unacceptable. This is right now. I leave the tab inactive to work on another tab and the memory consumption gradually increases. This is so annoying.

Ref: https://forums.opera.com/topic/36625/solved-opera-keeps-eating-up-my-memory

So I disabled all my extensions and re-tested and it's still happening. Please fix this issue. I'm way too invested into the Opera ecosystem to start using a different browser.

Already reported it to Chromium, you guys and the extension developers....lets see who actually does something to fix it.

Seems that this extension that serves a great purpose is no longer working. The devs for the extension have already been notified of the findings I've come across, they said it's on Opera to make the necessary changes within the browser, supposedly. Please see what can be done. https://github.com/gorhill/uBO-Extra.

Ublock Origins Extra. - Some of us really do care.
Purpose
To foil hostile anti-user mechanisms used to work around content blockers or even privacy settings in a browser.

Instart Logic's technology used to disguise third-party network requests as first-party network requests, including the writing/reading of third-party cookies as first-party cookies. I consider this to be extremely hostile to users, even those not using a content blocker, as it allows third-party servers to read/write cookies even if a user chose to block 3rd-party cookies through your browser setting.

The company behind the technology understands how hostile its technology is to users, and thus tries to hide what is being done by making it difficult to investigate by detecting whether the browser's developer console is opened, and when it detects it is opened, it ceases completely to make use of the obfuscation mechanism. The developer console-detecting code works only for Chromium-based browsers however, and therefore the obfuscation technology is not used when using Firefox (a different web page is served for Firefox).

P.S. - An actual response from someone would be appreciated.

So I did some testing using the built-in developer tools on the support.com website and it seems that the issue lays in the JS loading times. I had an extension enabled (Ublock Origins Extras) that was causing the load times to increase exponentially, I disabled the extension and recreated my work environment and seems that the tabs memory has not increased. Currently the tab is sitting at 166mb, still very odd that all of a sudden that extension that has been enabled on previous builds of Opera is now acting up, plus that extension was updated regularly. Very odd.