dbeaver / dbeaver/dbeaver

CPU 100%

Open
#36,937 10 comments 0 reactions 0 assignees View on GitHub
performance x:oracle xo:eclipse xo:linux
Dominant language
Java
Stars
51.8k
Forks
4.4k
Avg merge
3d 13h
Merged PRs (30d)
183

Description

### Description

I am using Linux Mint 20.2 and I utilize multiple workspaces. I work with Oracle and manual transactions in Read Committed mode.

I don’t understand why I have to confirm each select with a commit—it’s quite illogical (unlike Plyxon and SQL Developer, which handle it much better). However, more problematic is when I forget to commit and switch to another workspace to work on something else, my CPU load jumps to 100% after a few minutes.

The cause is DBeaver, which tries to handle the uncommitted transaction (a dialog box appears).

Interestingly, when I simply switch back to the workspace where DBeaver is running, the CPU usage immediately drops.

### DBeaver Version

24.3.2

### Operating System

Linux Mint 20.2

### Database and driver

Oracle 23.2.0.0

### Steps to reproduce

1) On linux workspace number 3, I execute in Dbevear a command in Oracle, for example, "select user from dual," with manual transaction control.
2) I switch to any other workspace and continue working - not use Dbevear.
3) run terminal and top command
4) After about two minutes, the Java process (DBeaver) is at 100% CPU.
5) I switch back to workspace 3, do nothing, and the CPU load immediately decreases - and I see a dialog box asking if I want to commit.

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.