Opera 76 Stable
-
l33t4opera last edited byHi @stolis, does it crash also, when you launch the Opera with the following switch:
"Path\to\launcher.exe" --no-experiments? -
-
stolis last edited by stolis
@l33t4opera: If this is the right one ("C:\Program Files\Opera\launcher.exe" --no-experiments), yes. Same msg again. It's the only site shows it by the way. Everything else works fine.
-
l33t4opera last edited by l33t4opera
@stolis It crashes exactly on https://eztv.re or on some other specific subpage?
Try to run the Opera with another switch: "--disable-extensions" and see if this helps. If it does remove the switch and relaunch the browser, disable extensions one by one and see which one is the culprit.
Additionally, you can check if the crash happens also under fresh profile, by launching the Opera as follows:
"\Path\to\launcher.exe" --user-data-dir="\Path\to\writable_dir\fresh_profile". -
stolis last edited by stolis
@l33t4opera: A couple of seconds, after entering the home page (the one i 've mentioned). It passed my mind disabling extensions but i wonder 'cause it happens only in 76 while in 75 works just fine. I'll try your advises though i 'm not sure about the second one and espessialy about the (\Path\to\writable_dir\fresh_profile). Can you please be more specific? Thanks.
Don't know if it has any significance, but in "Slimjet" (with the same extensions) the page works just fine.
PS. Have you tried the page to check it out?
-
l33t4opera last edited by l33t4opera
@stolis The "fresh_profile" is the path to new Opera's profile (it will be created automatically by the Opera), you can set the path to any folder to which the user you use to run Opera has write permission to.
Yes I checked it and it doesn't crash here, but I'm currently on the other OS and the issue can be platform specific.
-
A Former User last edited by A Former User
@kened: I do not like formal and rigid forums' posts. People are full of emotions, all sorts of. Forcing them to vapid artificial words and expressions here is against human nature. Of course, I like your avatar!
It specially look good in full view:
Something is botched up in forums. I cannot upload images.
-
dwing last edited by
Why when switching from last visited workspace to any another workspace the active tab selected randomly instead of starting from last left in previous session active tab ? This behavior is not correct, stupidly enraging and annoying!
Please do so that when you are switching to another workspace the work starts from the tab that was left last including blank tab page.
-
stolis last edited by stolis
@l33t4opera: Well, this browser can drive you nuts. After disabling the extensions it seemed that "uBlock Origin" (very important to me ) was 'causing the problem.
After trying a few times disabling-reenabling it (in order to be sure), suddenly the problem disappeared.
I really have know idea what happened, do you?
I'll keep watching it to see how it goes and if needed i 'll write back. Though the "mystery" remains. Why now? Since i 've been using uBlock (more than 6 to 7 years now) this is the first time i faced such a problem. Don't know what to say.About the second option, does it matter if i use a path to another hard drive? What if i create a new folder like "New Profile" for example into the original "Opera Software" folder? Would that be a problem?
Thank you for the tips anyway
Update:
It seemed to good to be true, so ignore the first paragraph. It happened again. -
l33t4opera last edited by l33t4opera
@stolis You can open the "Extensions" page, click on the "Details" button for uBlock Origin, and enable "Developer mode" in the top right corner, then make sure "Collect errors" is enabled under the extension (it should be enabled by default) and see if it's displaying any error messages.
Also, you can go to the problematic website again, press "Ctrl+Shift+I", click on "Console" tab and see below if it displays any errors related to this extension.Anyway, now when we know the issue is related to the extension, maybe it will be easier for Opera's developers to find out the reason for that, if it's something in recent changes in Opera's code that causes the problem, or it's the extension's fault.
Perhaps the developers can discuss this with the author of the extension as well.It happens again even the extension is disabled?
-
stolis last edited by stolis
@l33t4opera: Nothing, no errors. From my point of view, it seems like 76 bug. Cause as i wrote above, it works just fine on 75 as well as on Slimjet browser.
I just hope they pay some attention to it since ublock is a very popular extension with a large number of users.
-
l33t4opera last edited by l33t4opera
@stolis I don't know which version of Slimjet you're using, but both: the recent SLJ and Opera 75 are based on the older, major version of Chromium and most probably that's why you don't experience the issue under them.
Anyway, SLJ is always a way behind of the other popular web browsers based on Chromium in updating it to the latest versions. -
-
tina Opera last edited by tina
@pavelopdev: Sorry, I can't confirm this issue. If you still experienced in performance problems on this website please report a bug to https://opera.atlassian.net/servicedesk/customer/portal/9
Btw, I also can reproduce an issue with #modal:galeria in other browsers ( not only Chromium based) -> https://imgur.com/p3icgRG
If you make a comparative analysis, it will be great if you make it on browsers with the same core version. And if you use different, it's also good to mention a number. It's hard to analyze by eye what versions you use. -
tina Opera last edited by
@alphablake: Can't reproduce this. Please report this problem to https://opera.atlassian.net/servicedesk/customer/portal/9 and attach logs from opera://media-internals
-
stolis last edited by
@l33t4opera: Can't tell if this happened due to a possible bug of chromium version or is it something else. I 'll have to wait and see. Right?
About SLJ delays this isn't necessarily bad. Maybe they wait in order to gather the most common problems that appear after every chromium update before they issue an update. The point is that doesn't create such problems. Who knows. -
A Former User last edited by A Former User
@tina said in Opera 76 Stable:
@pavelopdev: Sorry, I can't confirm this issue.
It's rather good news. There're umpteen dependencies, very subtle sometimes.
If you still experienced in performance problems on this website please report a bug to
Thank you, but I was answering to @adam1709, I do not use X-com and such issues are utterly meaningless to me, to bother with them more.
Btw, I also can reproduce an issue with #modal:galeria in other browsers ( not only Chromium based) -> https://imgur.com/p3icgRG
Thank you. Your information about other browsers told us the Opera browser is not the culprit harassing clients of X-com website.
If you make a comparative analysis, it will be great if you make it on browsers with the same core version.
Yes, good point. I use latest versions usually, so I did forget to pay attention to browsers' version numbers. My signature tells a lot, but describing web browsers' issues I'll try to impart more details.
-
dwing last edited by
@tina: Very sad You can not reproduce. But that is the reality.
When you start Opera with multiple workspaces and when switching from last left workspace to any another workspace then you find yourself on any tab, but not on last left one. Terrible & annoying!
Pls let it begin from last left active tab.
-
palx last edited by palx@dwing So from what you just wrote, it is safe to assume that what you mean is, that you experience that bug when you open Opera for the first time? Yes, it indeed messes what the last active tab on each Workspace was before you've closed it, and it is a nuisance...
But I get the feeling that what the Moderators, as well as, all of us others understood when you first reported the bug, is that it messes with the last active tab, even after you've cycled already on all the Workspaces, and get back to one and find a wrong tab active... Please, correct me if I am wrong.
-
l33t4opera last edited by
@stolis Most probably that's the reason, since it doesn't occur in previous versions of Chromium in both browsers. For sure the developers and the author of the extension should figure it out.
Regarding SLJ, it's not good (if not bad), that they don't update Chromium to a newer, major versions more often, mainly for security reasons, also many other, serious bugs may still exist in the code.
