Bug 299194

Summary: Uncaught Exception: Debugger domain already enabled
Product: WebKit Reporter: scottyangke
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: ap, inspector-bugzilla-changes, rcaliman
Priority: P2    
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
See Also: https://bugs.webkit.org/show_bug.cgi?id=284114
Attachments:
Description Flags
22 none

scottyangke
Reported 2025-09-19 11:13:32 PDT
Created attachment 476804 [details] 22 Uncaught Exception in Web Inspector. Steps to Reproduce: 1. What were you doing? Include setup or other preparations to reproduce the exception. 2. Include explicit, accurate, and minimal steps taken. Do not include extraneous or irrelevant steps. 3. What did you expect to have happen? What actually happened? Uncaught Exceptions: ----------------------- - Debugger domain already enabled (at :undefined:undefined) _dispatchResponseToPromise @ manifest-yr1khc1r.js:37:92927 _dispatchResponse @ manifest-yr1khc1r.js:37:92039 dispatch @ manifest-yr1khc1r.js:37:91045 dispatch @ manifest-yr1khc1r.js:37:85272 connect/< @ manifest-yr1khc1r.js:37:1537 ? @ ----------------------- Notes: Inspected URL: (unknown) Loading completed: true Frontend User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0
Attachments
22 (2.38 KB, text/vnd.trolltech.linguist)
2025-09-19 11:13 PDT, scottyangke 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2025-09-19 19:00:36 PDT
This report is not about WebKit. Unfortunately, there are instructions out there where a vendor of modified forked code wrongly advises to file their bugs against WebKit.
Razvan Caliman
Comment 2 2025-09-22 07:44:25 PDT
This is likely a bug created from running the Web Inspector from Bun See also: -https://bugs.webkit.org/show_bug.cgi?id=284114 -https://bugs.webkit.org/show_bug.cgi?id=293589 Please file an issue with that project: https://github.com/oven-sh/WebKit
Note You need to log in before you can comment on or make changes to this bug.