You can run installer with --launchopera=0 switch and later start Opera with --disable-update.
@DrNostromo do you have any AV that could affect this particular build? Do you have installed all latest system updates?
Do more on the web, with a fast and secure browser!
Download Opera browser with:
We are aware of this issue and trying to find root cause. Could you try starting Opera with --disable-gpu command line argument? If it works could you try changing default wallpaper and start Opera without --disable-gpu parameter?
This is not related to adblocker. It's one of built in extensions which allows context menu copy/paste to work on docs.google.com. In non chromium browser a popup appears asking to install chrome extension to allow this. To avoid this popup Opera uses built in extension to allow this, which has a drawback of adding this enforced permissions.
So some info from developer.
In regular situation there shouldn't be multiple entries of scheduled tasks. Each installer should keep it clean and have only one task created. When multiple scheduled tasks are present described situation can occur. Each tasks first attempts to lock temp folder for it's process. If it is not possible it will try to lock downloads, home and folder with launcher.exe where it will store temporary autoupdate files.
@wawood8 could you send us screenshot of the problem you see? I see @burnout426 assumes that it's installer issue but considering you mention lot of Opera processes it seems to be rather problem with installed browser itself.
If indeed installer is finished but browser goes white, could you try starting browser with switch --disable-gpu. This should disable hardware acceleration which is most common cause for problems with displaying content.
@timezer0 the ones I mentioned could be expected requests. There also could be request for some favicons or other resources related to Speed Dial tiles on opera:startpage. Also for clean profile we display https://www.opera.com/client/welcome page which does make requests to Google, Facebook and Yandex for statistics.
Could you try to use for example https://www.telerik.com/fiddler (not sure if it will catch all request though) or some other tool so we could actually see what requests those are exactly?
@timezer0 which version of Opera you are exactly using? Here are possible legitimate request that could be happening in background:
Yandex - could be Zen news on opera:startpage but used currently on beta and developer in Russia
Facebook - some requests to messenger on sidebar?
Google - widevine updates?
Could you check which Opera process is actually hogging the memory? To do so run built-in task manager which can be run through developer menu.
As for the relunching through opera:about page we know there can be some timing issue. Relunch button can appear before whole update process has finished and when it's pressed right away it could possibly lead to a broken update experience.
Tracking this internally as https://bugs.opera.com/browse/DNA-73425. We seem to had some success with reproducing itwith network bandwith 50kb/s. Also we managed to reproduce it on chromium (using different UA string there than default) and we already have logged there probably related issue https://bugs.chromium.org/p/chromium/issues/detail?id=898134
https://dev.opera.com/extensions/apis/ might not be exactly up to date.
activeTab - it's just 'tabs' API but with limited scope and we support it
gcm - partial support, that's why Join application isn't working correctly. It relies on https://developer.chrome.com/apps/instanceID which we do not support.
As for Pushbullet I did not have any problem with sending files between Chrome and Opera, so is this somehow limited for devices?
@panosv have been trying to reproduce it, but didn't encounter it even single time. Could you describe your steps exactly? Every little detail could be crucial here. What I've been doing:
Do you have any extensions installed? Any settings changed?
We already fixed this issue internally so should be available with next stable update.
@bluewinner22 could you try running Opera.app from console? Hopefully there should be some error logs with more details. Also do you get any system dialog with any error message?