Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DBeaver Crashes When Clicking Outside Window on Multi-Screen Setup #33195

Open
Aristevao opened this issue May 17, 2024 · 1 comment
Open

DBeaver Crashes When Clicking Outside Window on Multi-Screen Setup #33195

Aristevao opened this issue May 17, 2024 · 1 comment

Comments

@Aristevao
Copy link

Aristevao commented May 17, 2024

Description

I have encountered a recurring issue while working with DBeaver on a dual-screen setup, comprising a notebook and a second screen. The problem arises when I am actively working within the DBeaver window and subsequently click anywhere on the second screen or vice versa. Invariably, this action triggers a crash of the DBeaver application.

Notably, the issue persists even during the app's startup phase, exacerbating the inconvenience. This behavior has been consistent across multiple versions, including the latest release, as well as several preceding versions that I've tested.

After updating to the latest Java 17 version, the crashes reduced, but didn't cease.

DBeaver Version

Comunity Edition 24.0.4.202405051837

Operating System

Windows 10

Database and driver

Database: PostgreSQL 14.6
Driver: PostgreSQL JDBC Driver 42.2.5

Steps to reproduce

  1. Launch DBeaver on a dual-screen setup.
  2. Click within the DBeaver window.
  3. Click anywhere on the second screen or vice versa.

Expected Results

Normal functioning without any crashes or disruptions when interacting with different screens while the DBeaver application is active.

Actual Results

DBeaver crashes every time there is an interaction between the DBeaver window and the second screen, leading to a disruption in workflow.

Additional context

Did it work before?

  • It worked several months ago.

Java version:

  • Current: 17.0.11 2024-04-16 LTS
  • Previous : 11.0.17 2022-10-18 LTS

When updated to java 17.0.6 2023-01-17 LTS the problem ceased temporarily.
This action triggers a crash of the DBeaver application yet, but not every time as before.

When I open the application again after the crash, it doesn't show any log error. If I can find it anywhere, please, let me know.

@E1izabeth
Copy link
Member

We would kindly ask you to reproduce the issue once again. After you reproduce the issue, please send us the DBeaver log files.
The log files are generated automatically and called .log and .dbeaver-debug.log exactly. They are located in the %APPDATA%\DBeaverData\workspace6.metadata directory. Here is our wiki page on this matter: dbeaver.com/docs/wiki/Log-files/#log-files

If there are some java fatal logs dbeaver.com/docs/dbeaver/Log-files/#java-fatal-log, please provide them too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants