Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
After update to 2.0.54 my extension “Oracle SQL Develope Extension for VSCode” is stuck while activating. The extension has a message displayed at the bottom status bar that says “Activating Oracle SQL Develope Extension for VSCode…” which normally takes 5-10 seconds. It has been stuck for 1 hour today.
Extension Details:
Oracle SQL Developer Extension for VSCode
Identifier: oracle.sql-developer
Version: 24.4.1
Last Updated: 2024-12-20, 22:30:56
Steps to Reproduce
Restart Cursor, wait for activation
Expected Behavior
Extension activates in 5-10 seconds and I can start using it.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.0.54 (user setup)
VSCode Version: 1.99.3
Commit: 7a31bffd467aa2d9adfda69076eb924e9062cb20
Date: 2025-11-03T22:40:44.657Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
For AI issues: which model did you use?
NA
For AI issues: add Request ID with privacy disabled
NA
Does this stop you from using Cursor
No - Cursor works, but with this issue
3 Likes
This continues to not function in the following version of Cursor. I also noticed that the extension no longer appears in the Extensions marketplace in Cursor. I downloaded the VSIX for version 25.1.1 from VSCode’s marketplace, this is the lastest version that is compatible with VSCode Version: 1.99.3. This newer version of the Oracle extension also does not work.
If there’s anything else I should try please let me know. I see that I’m one of a few that is using this extension with Cursor (at least that comes to this forum), but this has a heavy impact on my workflow. I’m back in VSCode because running queries and seeing results in my IDE is far more important that AI tasks. I’m now performing AI tasks on chatgpt.com and pasting back and forth. It’s like 2024 again, lol.
Cursor Version
Version: 2.0.64 (user setup)
VSCode Version: 1.99.3
Commit: 25412918da7e74b2686b25d62da1f01cfcd27680
Date: 2025-11-06T04:35:14.424Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
I added trace logging and found that DBToolsServerApp is being terminated within a few seconds of spawning. Some investigation mostly with AI chats suggest that its a sandboxing issue (but this is not my area and AI is not always accurate).
[11/06/25, 14:19:03.494] [DBToolsServerApp] [DEBUG] startServer: DBToolsServerApp
[11/06/25, 14:19:03.513] [DBToolsServerApp(7520)] [DEBUG] spawning
[11/06/25, 14:19:03.513] [dbtools-client ] [INFO ] Server startup completed
[11/06/25, 14:19:04.114] [DBToolsServerApp(7520)] [INFO ] Process terminated with exit code 1 due to receipt of signal null