"Profile Error Occurred" - Message On Opera Startup

andrius-s

andrius-s @leocg

@leocg said in "Profile Error Occurred" - Message On Opera Startup:

@andrius-s What about Opera 70?

Already updated to 70.0.3728.71. I will keep my eyes on it and will inform on this thread...

tapedi2471

tapedi2471

70.0.3728.95, Profile Error, no cookie wipe.

tapedi2471

tapedi2471

70.0.3728.106, cookies wiped. I've noticed that the size of Cookies file did not decrease when they got wiped.

avmon

avmon @tapedi2471

@tapedi2471 Yes, the file size is almost the same as the backup that I made before. The error happened to me again a few days ago with Opera 70. Instead of fixing long-lasting bugs like this, they are dedicated to removing good features.

tapedi2471

tapedi2471

I've checked the bad Cookies file in SQLite browser and hex editor: 90% of records are wiped (zeroed), but the remaining ones are spread throughout the file (not just at the beginning).

tapedi2471

tapedi2471

I've compared "profile error" logs with and without cookie wipe.
Without:

>**VERBOSE1:first_run_detector_impl.cc(150)] No version change detected. Assuming normal run.**
>VERBOSE1:pref_proxy_config_tracker_impl.cc(185)] 0000000000595CD0: set chrome proxy config service to 0000000000596130
>WARNING:process_singleton_win.cc(345)] Will attempt to lower process integrity level.
>VERBOSE1:statistics_recorder.cc(428)] Collections of all histograms
>VERBOSE1:statistics_recorder.cc(428)] Collections of all histograms
>**VERBOSE1:first_run_detector_impl.cc(150)] No version change detected. Assuming normal run.**
>VERBOSE1:pref_proxy_config_tracker_impl.cc(185)] 00000000004147D0: set chrome proxy config service to 0000000000414C30
>WARNING:process_singleton_win.cc(345)] Will attempt to lower process integrity level.
>VERBOSE1:component_update_scheduler_impl.cc(88)] Registered component Partner Content Autoupdate
>VERBOSE1:component_update_scheduler_impl.cc(190)] Next component update check in 60 s
>VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: https://autoupdate.geo.opera.com/geolocation/
>VERBOSE1:component_update_scheduler_impl.cc(88)] Registered component PrefsOverride
>VERBOSE1:component_update_scheduler_impl.cc(88)] Registered component sitepatcher_opautoupdatechecker
>VERBOSE1:component_update_scheduler_impl.cc(88)] Registered component sitepatcher_opautoupdatechecker_siteprefs
>ERROR:os_crypt_win.cc(92)] Failed to decrypt: The parameter is incorrect. (0x57)
>VERBOSE1:pref_proxy_config_tracker_impl.cc(185)] 00000000084C4F20: set chrome proxy config service to 000000000344F440
>VERBOSE1:token_cache_impl.cc(28)] Token cache created.
>VERBOSE1:token_cache_impl.cc(37)] Token cache initializing.
>**VERBOSE1:persistent_session_impl.cc(140)] Loaded session in state INACTIVE for user_id**

With:

>**VERBOSE1:first_run_detector_impl.cc(150)] No version change detected. Assuming normal run.**
>VERBOSE1:pref_proxy_config_tracker_impl.cc(185)] 0000000000434CD0: set chrome proxy config service to 0000000000435130
>WARNING:process_singleton_win.cc(345)] Will attempt to lower process integrity level.
>VERBOSE1:statistics_recorder.cc(428)] Collections of all histograms
>VERBOSE1:statistics_recorder.cc(428)] Collections of all histograms
>**VERBOSE1:first_run_detector_impl.cc(46)] Unable to fetch version from list.**
>VERBOSE1:first_run_detector_impl.cc(122)] Last version not found. Assuming first run ever.
>VERBOSE1:pref_proxy_config_tracker_impl.cc(185)] 00000000021870A0: set chrome proxy config service to 0000000000679200
>WARNING:process_singleton_win.cc(345)] Will attempt to lower process integrity level.
>VERBOSE1:component_update_scheduler_impl.cc(88)] Registered component Partner Content Autoupdate
>VERBOSE1:component_update_scheduler_impl.cc(190)] Next component update check in 60 s
>VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: https://autoupdate.geo.opera.com/geolocation/
>VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: https://autoupdate.geo.opera.com/geolocation/
>VERBOSE1:component_update_scheduler_impl.cc(88)] Registered component PrefsOverride
>VERBOSE1:component_update_scheduler_impl.cc(88)] Registered component sitepatcher_opautoupdatechecker
>VERBOSE1:component_update_scheduler_impl.cc(88)] Registered component sitepatcher_opautoupdatechecker_siteprefs
>ERROR:os_crypt_win.cc(92)] Failed to decrypt: The parameter is incorrect. (0x57)
>VERBOSE1:pref_proxy_config_tracker_impl.cc(185)] 0000000008AE8690: set chrome proxy config service to 0000000008AE8980
>VERBOSE1:token_cache_impl.cc(28)] Token cache created.
>VERBOSE1:token_cache_impl.cc(37)] Token cache initializing.
>**VERBOSE1:persistent_session_impl.cc(135)] Loaded broken session, treating as empty.**
>VERBOSE1:persistent_session_impl.cc(219)] Changing state from UNSET to INACTIVE

Notice, that first_run_detector_impl.cc and persistent_session_impl.cc are not the Chromium code. And the whole problem is likely triggered by some Opera telemetry collection code in statistics_recorder.cc.

tapedi2471

tapedi2471 This post is deleted!

andrius-s

andrius-s

Long story short: Me and many other users of Opera for Windows browser are experiencing the same issue - "Profile Error Occurred" message appears on Opera Startup:
Right after this issue I'm losing all login (active sessions) data and settings of the individual Web-Sites. It looks like wiping all Cookies, but I do confirm - the switch named as "Clear cookies and site data when you quit Opera" is always OFF in my program.
At the beginning of May, 2020 I have decided a radical experiment: to uninstall an Opera browser fully, to clear any traces from this program and then reinstall it from the scratch again. Unfortunately, now I can state, the problem is still present on the latest versions of Opera (currently I'm using 70.0.3728.119 on Windows 7 x64 i7 machine). Latest occurrence has been observed today (as of 24th August, 2020).
Few months ago some users have discovered that instance of the file "...\AppData\Roaming\Opera Software\Opera Stable\Cookies" could bring all the lost settings back by restoring this file from backup.
The testing is quite annoying, because this problem occurs just in some occasions. I cannot find any reasons and clues about it. Sometimes even I don't get a "Profile Error Occurred..." message, but some configuration is nevertheless lost.
It looks like this issue is tending to appear of more frequent when Windows OS is freshly restarted.
You can read some findings from other users about this problem on the old topic here.
Anyway, this problem isn't resolved jet and I encourage developers of Opera browser to pay some attention into this problem.

leocg

leocg Moderator Volunteer This post is deleted!

sgunhouse

sgunhouse Moderator Volunteer

Never run Opera as administrator, as this will result. Beyond that, you'd have to tell us what you did to cause it.

andrius-s

andrius-s @sgunhouse

@sgunhouse said in "Profile Error Occurred" - Message On Opera Startup:

Never run Opera as administrator, as this will result.

Yes, currently I'm logged as Administrator on my Windows 7 OS... Why can't I use Opera with an administrator account?

Beyond that, you'd have to tell us what you did to cause it.

I cannot describe any rules or consistent behavioural pattern of when this problem occurs. I'm using Opera as my default browser on Windows 7 64x OS. Usually, there are about 10-15 opened Tabs at the moment I'm closing my Opera browser. It is configured to restore all Tabs on the startup. And this problem appears when I'm starting my browser. Though, it doesn't happen on every startup of the browser.
As I have written earlier, it looks like this issue is tending to appear of more frequent when Windows OS is freshly started.

sgunhouse

sgunhouse Moderator Volunteer

Using an administrator account in Windows is not the same thing as running a program as administrator. If you right-click on a program one of the options will be Run as administrator. If you select that option, Windows will display a UAC dialog asking if you want the program to be allowed to make changes to your computer (like most installers display) and any files changed by that program will require administrator access to be changed in the future. So if you one time run Opera as administrator, the next time you run Opera normally it will be unable to save changes to its cookies, bookmarks or even history. The only fix would be to copy all the files, as administrator delete the entire profile, the as a regular user copy everything back - if a regular user tries to delete the profile it will silently fail.

A Former User

Opera 70.0.3728.119. The problem remained, dear developers - how long will this problem be solved?

avmon

avmon

In my case I have Opera configured to start only with Speed Dial.
The error only happens to me sometimes but always when opening Opera for the first time after starting Windows.
As it seems to be related to the high demand on system resources from other processes after starting Windows, I usually try to wait a bit to start Opera. In this way it seems that the error occurs much less often.
My system: Intel i7 8GB - Windows 7 x64

andrius-s

andrius-s @sgunhouse

@sgunhouse said in "Profile Error Occurred" - Message On Opera Startup:

Using an administrator account in Windows is not the same thing as running a program as administrator. If you right-click on a program one of the options will be Run as administrator. If you select that option, Windows will display a UAC dialog asking if you want the program to be allowed to make changes to your computer (like most installers display) and any files changed by that program will require administrator access to be changed in the future. So if you one time run Opera as administrator, the next time you run Opera normally it will be unable to save changes to its cookies, bookmarks or even history. The only fix would be to copy all the files, as administrator delete the entire profile, the as a regular user copy everything back - if a regular user tries to delete the profile it will silently fail.

Thank You for the specification... Then this issue isn't related to the case of running a program as administrator: I have never used an option "Run as administrator" with Opera browser. Additionally, at the beginning of May, 2020 I have done full uninstall of Opera browser, then cleared any traces from this program and then reinstalled it from the scratch again. In this way, the whole profile has been re-created newly. But anyway, an irregular "Profile Error Occurred..." problem on Opera startup still persists... Latest occurrence has been observed 4 days ago (Opera v70.0.3728.119 on Windows 7 x64 i7 machine).

andrius-s

andrius-s

Latest occurrence (wiped Cookies) has been observed today (as of 29th August, 2020, Opera 70.0.3728.119)...

A Former User

As the original poster of this thread way back in July 2019 I am surprised Opera has not taken on board any of these comments. Do the Opera developers ever read these forums which is the only way most of us are able to voice our concerns. I suppose if I lived in Norway I would actually go into their offices to complain. All I can assume is Opera employees must work with glazed eyes thinking how good their browser is and gladly pick up their salary check each month. Well Opera is not perfect, no browser is perfect but there are alternatives like Vivaldi that I get on well with.

avmon

avmon @andrius-s

@andrius-s Today, it has happened to me again (Opera 70.0.3728.133).

blackbird71

blackbird71 @Guest

@mike88 said in "Profile Error Occurred" - Message On Opera Startup:

As the original poster of this thread way back in July 2019 I am surprised Opera has not taken on board any of these comments. ...

As has been posted by @andrius-s above: "I cannot describe any rules or consistent behavioral pattern of when this problem occurs." For a developer to identify the problem cause, it is virtually essential that they be able to duplicate it on a system they can monitor - otherwise, they're working in the dark and purely guessing about causes.

To duplicate the problem, a troubleshooter needs to know (for each user seeing the problem): the OS and its version, the Opera version involved, the list of extensions installed into the browser, and a list of the steps that occurred prior to the problem onset (much as @andrius-s has done in this thread). But even with that information, an intermittent or inconsistent problem behavior will take considerably longer to track down, hence it inevitably will require a lot more time and effort on the developers' part. That has to be taken into account, given the existing workload of other problems and ongoing new-design efforts.

"Way back in July 2019" is not that far back for tracking down and solving a problem that even those actually seeing it can't consistently duplicate.

burnout426

burnout426 Volunteer

Check the status of your hard drive with CrystalDiskInfo. Make sure your hard drive is in good condition.
Wipe out your hard drive, install Windows fresh, and update windows.
Download Opera (latest version) and install it fresh. Do not restore a backed-up Opera profile, do not import anything into Opera, do not install any extensions, and do not enable Opera Sync. Also, do not install any extra security software on Windows.

Use Opera and Windows like that for a while to confirm that everything works fine (if you can reproduce in that case, that'd be interesting). Then, slowly do more things and see if you can figure out what triggers it.

It's probably a corrupted Opera profile (due to hard drive being bad or improper shutdown of Opera and or the computer, or Opera Sync) or corrupted user account on Windows or some corrupted system files on Windows (due to bad hard drive or improper shutdown).

If you found out that it's when you sync, you'll need to start with a new Opera profile again, and wipe things out at sync.opera.com, and start syncing from scratch.

Unfortunately, if the problem is due to some corruption, if you just keep using Opera, Opera Sync, and Windows as-is, you'll probably never see a fix for this.