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 on Windows 11 arm64 #18527

Open
JorgeGarciaEnki opened this issue Dec 17, 2022 · 11 comments
Open

DBeaver on Windows 11 arm64 #18527

JorgeGarciaEnki opened this issue Dec 17, 2022 · 11 comments

Comments

@JorgeGarciaEnki
Copy link

Hello,

I currently use a MacBook Pro with M1 Pro. I tried to run Windows 11 on arm with the new VMWare Fusion and Parallels to run some programs which don't exists on MacOS.

I tried DBeaver for 64 bits and it "works" under this configuration but I get a lot of crashes randomly on my day.

I know this is normal because Win11 on arm64 is currently on development.

There are plans to release a DBeaver version for win arm64?

Thanks.

@Destrolaric
Copy link
Member

@JorgeGarciaEnki Hi, we are currently waiting for our framework to start building Windows arm64 SDK.
You can look at the status of that process in the following issue:
eclipse-platform/eclipse.platform.releng.aggregator#577
For now we can't bundle arm64 build

@JorgeGarciaEnki
Copy link
Author

Good News @Destrolaric!

Looking forward to try it.

Thanks!

@chirontt
Copy link

@JorgeGarciaEnki Win-arm64 has a x64 translation layer, so that an x64 application like DBeaver can run successfully.

I don't have a Mac, but I have a native win-arm64 box, and on this box I can run this DBeaver zip successfully, at least with the sample SQLite database provided. The trick is to force DBeaver to use an explicit x64 JDK/JRE, by modifying its dbeaver.ini file with an explicit -vm entry that points to an x64 JDK/JRE available on the system. (By default, I have a native arm64 JDK, and this JDK can't be used with the above DBeaver which was built for x64.)

@chirontt
Copy link

@Destrolaric Is DBeaver (the community version) available on the Eclipse update sites?

I have an Eclipse SDK (a bare-bone Eclipse) already built for win-arm64. Can I use the Eclipse update sites to manually update my Eclipse SDK with all DBeaver plugins? The idea is to manually "build" the DBeaver product with this Eclipse SDK for win-arm64 via the Install New Software facility in Eclipse...

@JorgeGarciaEnki
Copy link
Author

Hello @chirontt,

Yes It work the 64bit version but in my case it randomly crashes, sometimes won't even open (show the initializing splash and then it dies), sometimes a few minutes after the app started and sometime after of hours of using it. Random.

I'm using the vertica driver (downloaded from dbeaver connection wizard) to my daily use.

@chirontt
Copy link

chirontt commented Dec 27, 2022

@JorgeGarciaEnki I have no experience with the Vertica database, so I can't comment much about it. But what you described sounds like some problems between DBeaver and Vertica, rather than with the Windows Arm64 platform. Have you tried to reproduce the problems on a real Windows 11 box (not in a VM)?

If you want to try a Windows Arm64 (unofficial) version of DBeaver, I have created a zip package for it here in my fork of DBeaver. Note that this package need a native Windows Arm64 JDK to run, such as the Arm64 JDKs available from Microsoft, Liberica, or Zulu.

@JorgeGarciaEnki
Copy link
Author

Hello @chirontt,
I've downloaded your package and currently testing with Microsoft JDK.

I get back to you in a few days for testing results.

Thank you!

@technobrat-us
Copy link

@JorgeGarciaEnki I have no experience with the Vertica database, so I can't comment much about it. But what you described sounds like some problems between DBeaver and Vertica, rather than with the Windows Arm64 platform. Have you tried to reproduce the problems on a real Windows 11 box (not in a VM)?

If you want to try a Windows Arm64 (unofficial) version of DBeaver, I have created a zip package for it here in my fork of DBeaver. Note that this package need a native Windows Arm64 JDK to run, such as the Arm64 JDKs available from Microsoft, Liberica, or Zulu.

Hi @chirontt, I'm about to receive a Lenovo X13s with ARM Snappdragon CPU and I'm kind of preparing myself with the tools I need for work. One of them is Dbeaver. So DBeaver does not work correctly in Win11 emulation hence your solution?

If so, how has your experience with this unofficial ARM solution, crashes are expected?
Thanks for the feedback.
LF.

@chirontt
Copy link

chirontt commented Feb 2, 2023

@technobrat-us As I mentioned before, the official DBeaver release for x64 platform can be run as-is on a Windows Arm64 platform, due to the x64 translation layer available in Windows Arm64 for all x64 software. The DBeaver release also includes an embedded JRE (for x64), so it's self-contained and can run without any external JRE/JDK required.

The caveat is that it will be slower than a native Arm64 version, inherently due to the x64 translation layer.

I've only used my unofficial Arm64 package sparingly now and then, but it works fine for me on my Windows Arm64 box. It runs faster than the x64 version, which was what I wanted in the first place (to get rid of the x64 translation layer.)

I suggest you should run the official DBeaver version for x64 on your Lenovo laptop first, and see how it goes, before deciding on whether to try my unofficial Arm64 version. If the x64 version works well enough (i.e. the laptop is powerful enough) then my Arm64 version may not be relevant for you, to avoid the risk of running "unofficial" software.

@AlexanderDash
Copy link

I want to know if compiling an installation package for Windows arm64 is easy. The translation of x64 is a bit sluggish..

@chirontt
Copy link

chirontt commented Feb 3, 2024

I have created zip packages for it here in my fork of DBeaver for Windows on Arm64. The page also shows how to build it yourself.

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

Successfully merging a pull request may close this issue.

6 participants