DevTools crashes Opera

[daria19]

daria19 Opera @Netergo last edited by

@Netergo Could you kindly provide us with the crash ID associated with this issue? You can find it in the opera://crashes page. It would greatly assist us in investigating the problem.

[Netergo]

Netergo @daria19 last edited by

@daria19 Most of the crashes in my case doesn't have an ID (Discarded=1). Only few have - this is one of those:
CrashID=bp-662a4fc8-ecd1-499c-911b-936da0250105

[rumgezuzzl]

rumgezuzzl @Netergo last edited by

@Netergo Same here. I don't have a single crash with an ID.

[rumgezuzzl]

rumgezuzzl last edited by

Problem persists in version Version: 116.0.5366.21.
On my machine it crashes exactly every second time I inspect an element.

This is a deal breaker, since I am a web developer and need this function all the time.

[Gekiyaku]

Gekiyaku last edited by Gekiyaku

Same issue here. When I inspect element it opens DevTools, but with DevTools opened when I click inspect again it crashes every time.
When I close DevTools I can inspect again no problem.

[Ljutyj]

Ljutyj @Gekiyaku last edited by

@Gekiyaku said in DevTools crashes Opera:

Same issue here. When I inspect element it opens DevTools, but with DevTools opened when I click inspect again it crashes every time.
When I close DevTools I can inspect again no problem.

Have the same problem. 115.0.5322.119 and 116.0.5366.21 (after an update that didn't help). I am a web developer and have been using Opera for over 15 years. I'm used to it. But now it is completely unusable. I can't work. It's horrible.

[tomaustin]

tomaustin @umutkazdal last edited by

Same problem, I get it when:
a. DevTools is already open
b. I click the F12 key

Browser closes and then reopens.

[duviii]

duviii last edited by

Same here, happening on latest v115 and current v116

[tomaustin]

tomaustin @tomaustin last edited by

This bug is now making Opera unusable for development purposes.

I've now given up waiting for a patch and have reinstalled a December 2024 version of Opera instead, over the current version.

I went to this version: https://get.opera.com/ftp/pub/opera_gx/115.0.5322.113/win/

DevTools is now working OK.

[SlymoDev]

SlymoDev last edited by

any fix for this on the way?

[rumgezuzzl]

rumgezuzzl @tomaustin last edited by

@tomaustin Alas if I downgrade Opera, autoupdate kicks in and restores the latest version.
Frankly I don't understand why Opera cannot solve this problem, obviously it is a regression, the version where it started is well known, just have to look at version control.

[tomaustin]

tomaustin @rumgezuzzl last edited by

@rumgezuzzl sadly, you're right. It worked for about 20-30 minutes, and then autoupdate (which one can't switch off) came along and ruined things.

Opera Devs -- is anyone there? Is anyone looking at this?

[Gekiyaku]

Gekiyaku @tomaustin last edited by Gekiyaku

@tomaustin they are busy thinking where to put poo emojis next. No time for some nerdy devtools

[duviii]

duviii last edited by

Still crashing in 116.0.5366.35

[leocg]

leocg Moderator Volunteer @umutkazdal last edited by

@umutkazdal Doesn't seem to crash here on 116.0.5366.35 or in 118.0.5411.0

[ciachun]

ciachun @leocg last edited by

@leocg still crashing on Today's stable 116 build. Time to move to some other browser... Recent versions are sooo buggy and UI-unbaked...

[consultor-brtech]

consultor-brtech @Gekiyaku last edited by

@Gekiyaku ,

Exactly the same error here. if devtools is open and i click with the mouse or CTRL +SHIFT +C , it crashes, close and open again

Opera One(versão: 116.0.5366.35
Fluxo de atualização:Stable
Sistema:Windows 10 64-bit
Versão do Chromium:131.0.6778.266

[Mblaw]

Mblaw last edited by

Same here, shall I uninstall opera?

[Naser007]

Naser007 last edited by

I have just updated to 116.0.5366.35 and problem still exists.

[nkgrzegorzewicz]

nkgrzegorzewicz Opera @Naser007 last edited by

Thank you for bringing this issue to our attention and for your patience while we worked on a solution.
We’re happy to inform you that the issue has been identified and resolved. The fix will be included in our upcoming stable release, which is scheduled for next week!