Opera crashes on launch every time

A Former User

On Mac OS Catalina 10.15 every time I start Opera it crashes immediately. It even gets into a loop where it crashes, then reopens itself, and crashes again, and loops this way several times.
I cleared all the preference files in application support, etc. and tried to do a fresh install several times - didn't work.
I did log in as another user on the same computer and it launched just fine. So I copied the preference files from this user (including after changing the home page, disabled some features, etc.) but it still wouldn't work for me.
I updated my OS to the newest version, and it has the same problem still.
I looked through the Mac's Console and found no crash logs. There is no error or warning when it crashes, it just exits and starts to launch itself again.
When I launch it, it renders the UI but shows a blank page and "Loading" in the current Tab, for about 1 to 2 seconds, and then crashes.
I'm not running any strange antivirus apps or anything.
This problem means I can not use Opera at all. Can't even launch it. What can I do?

A Former User @Guest

@helloperahelloopera Bump - it's still doing it. Haven't been able to use this browser for months.

A Former User

So am I to understand that there is either no one willing or no one able to help me with this? To offer even a single suggestion?

I am a tech-savvy user, and am entirely unable to run Opera on my personal computer. Should I be telling all of my colleagues that Opera is totally unreliable and should never be installed on client computers because there is no guarantee that it can even launch? Should I tell them that it is untested buggy software with zero customer support?

leocg

leocg Moderator Volunteer @Guest

@helloperahelloopera Being this forum mainly for users to try to help each other, I guess the answer may be yes, no one has a solution for your problem.

Since you said that Opera works if you log in using a different credentials, maybe the problem is with the other user?

l33t4opera

l33t4opera @Guest

@helloperahelloopera You can try to rename the "Local State" file in the profile's folder, or launch the Opera from the command line with the switch "--no-experiments" as follows: /Applications/Opera.app/Contents/MacOS/Opera --no-experiments
Both should launch the Opera with default flags settings. If this helps, then you can overwrite the "Local state" file in broken profile, with the one in which Opera is launching fine.

A Former User @l33t4opera

@l33t4opera Hey, thanks for your suggestion. It didn't work but it at least led me to finally get an error message in console:

dyld: warning, LC_RPATH @loader_path/../../../../../../../../../.. in /Applications/Opera.app/Contents/Frameworks/Opera Framework.framework/Versions/68.0.3618.56/Helpers/Opera Helper.app/Contents/MacOS/Opera Helper being ignored in restricted program because of @loader_path (Codesign main executable with Library Validation to allow @ paths)

Does this mean anything to anyone?

l33t4opera

l33t4opera @Guest

Hi @helloperahelloopera, sorry for the late reply, I was busy several days.
Have you tried already to launch the Opera from the command line using a fresh profile as follows:
/Path/to/Opera --user-data-dir="/Path/to/freshprofile" Does it help?

stevenjcee

stevenjcee

I had this same problem, on both my computers, and nothing I did fixed it. Somehow, after totally removing & reinstalling it (after a few tries), it now is working OK, it could be the most recent update fixed something. So it seems to. be working, without instantly freezing, and running up all my RAM, the only issue now, is that I can't stream without it buffering and buffering.

blackdrago

blackdrago

I know this thread is over a year old, but I also have been running into this, too. There are times when my install of Opera works fine until I restart my computer, and then it falls into a loop of open/immediately fail and close (appearing and disappearinng on the toolbar as it does so).

When I try to run from the command line, I get this error:

dyld: warning, LC_RPATH @loader_path/../../../../../../../../../.. in /Applications/Opera.app/Contents/Frameworks/Opera Framework.framework/Versions/-OPERA-VERSION-HERE/Helpers/Opera Helper.app/Contents/MacOS/Opera Helper being ignored in restricted program because of @loader_path (Codesign main executable with Library Validation to allow @ paths)

Often uninstalling and reinstalling has no effect.

The only thing that works for me is a combination of 2 suggestions. First, per another old thread Opera endless loop of crashes:

rm -r ~/Library/Application\ Support/com.operasoftware.Opera

Then, per the suggestion above, run opera with no experiments:

/Applications/Opera.app/Contents/MacOS/Opera --no-experiments

I can only open Opera by the Terminal right now.

stevenjcee

stevenjcee @blackdrago

@blackdrago Wow, this is really sad. You shouldn't have to jump through all those hoops just to open a browser! And I don't know what to do, oddly enough, it seems to work ok on my 10-year old Macbook Pro, running High Sierra, but on my much newer iMac, running Catalina, with 64 Gigs of RAM, it's a total no-go. Soon as I open it, it will run for less than five minutes, then crash, over & over, it just won't stay open and work.... smh

stevenjcee

stevenjcee @stevenjcee

@stevenjcee Just downloaded yet another new, updated version, from the website. Installed it, looked good, but then a few minutes later it ran up CPU to 100% and showed "Opera not responding", so as usual, I had to force quit it. Why is this happening no matter how many times I install new updated versions?