-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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 crash at launch #4539
Comments
Can't reproduce. However it is clearly a bug in splashscreen handler. |
Hi Serge. Done in /Applications/DBeaver.app/Contents/Eclipse/dbeaver.ini, which is now: The splashscreen is still displayed and the same error occurs. |
Ok, thanks for checking this. |
Done. Still same behaviour:
|
Ok, then something else is guilty. I see that your Java version differs from the Java bndled in pkg. Could you try to install using PKG (download it from dbeaver.io or GitHub)? |
I have installed dbeaver-ce-5.2.3-macos.dmg from dbeaver.io. And now, no more blank window but only window action buttons: debug log file (attached): |
This is weird (I can't reproduce this on two Macs with Mojave). |
Hello Serge. Done with both releases (DMG and PKG). You will find attached the debug log files for both releases. |
Oops, the archive is password protected |
Oops, sorry. |
Apparently I've made a mistake during Early Access publishing (it is still old). Could you test the latest one (https://dbeaver.io/files/ea/) |
Same :/ |
This is a bug in Eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=540357 This error happens because DBeaver tries to switch to Dark theme (I assume that you using Mojave with dark theme). Please try this workaround: add line |
I have modified the dbeaver.ini as you suggested (-nospash parameter) Still have NullPointerException |
I am experiencing the same issue. Upgraded to Mojave and suddenly DBeaver no longer works. Upon start, I see the following as normal... However, after this loads, I see the menu bar options, but the actual editor windows do not open... Tried adding -nosplash to DBeaver.ini, but that didn't do anything. |
@lalato could you also post debug and error logs? |
Edited original post with debug log |
Just tried the trick of holding down the Ctrl key during launch. This seems to be working for me. |
@lalato thanks for details.
Wow. That's unusual. Thanks a lot for the information :) |
Hold down control worked for me. That was weird. Besides, the -nosplash option worked for 5.2.4 but not for 5.2.5. I am using Windows with the new dark theme. I think that is the same issue. |
Solved the issue for me: /Applications/DBeaver.app/Contents/Eclipse/dbeaver.ini
I only did add the first two lines with -vm and /Library/Java/... to the existing file. |
Thank you for the info @greyshine |
@greshyine s method works. I can confirm it. |
Hi,
Since Mojave installation, DBeaver crash at launch w/ blank Eclipse SDK window.
My conf:
log file (extract):
!SESSION 2018-11-05 14:34:19.102 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_191
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=fr_FR
Framework arguments: -keyring /Users/ylepors/.eclipse_keyring
Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/ylepors/.eclipse_keyring
!ENTRY org.eclipse.ui.workbench 4 2 2018-11-05 14:34:21.847
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
!STACK 0
java.lang.NullPointerException
at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2180)
at org.eclipse.swt.graphics.GC.(GC.java:177)
at org.eclipse.swt.graphics.GC.(GC.java:138)
at org.eclipse.jface.wizard.ProgressMonitorPart.initialize(ProgressMonitorPart.java:244)
at org.eclipse.jface.wizard.ProgressMonitorPart.(ProgressMonitorPart.java:141)
at org.eclipse.jface.wizard.ProgressMonitorPart.(ProgressMonitorPart.java:106)
at org.eclipse.ui.splash.BasicSplashHandler$AbsolutePositionProgressMonitorPart.(BasicSplashHandler.java:53)
at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:141)
at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.init(DBeaverSplashHandler.java:69)
at org.eclipse.ui.internal.Workbench$2.run(Workbench.java:833)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.ui.internal.Workbench.createSplashWrapper(Workbench.java:849)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:600)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
at org.jkiss.dbeaver.core.application.DBeaverApplication.start(DBeaverApplication.java:156)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
!ENTRY org.eclipse.ui 4 0 2018-11-05 14:34:21.851
!MESSAGE Could not instantiate splash
!STACK 0
java.lang.NullPointerException
at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2180)
at org.eclipse.swt.graphics.GC.(GC.java:177)
at org.eclipse.swt.graphics.GC.(GC.java:138)
at org.eclipse.jface.wizard.ProgressMonitorPart.initialize(ProgressMonitorPart.java:244)
at org.eclipse.jface.wizard.ProgressMonitorPart.(ProgressMonitorPart.java:141)
at org.eclipse.jface.wizard.ProgressMonitorPart.(ProgressMonitorPart.java:106)
at org.eclipse.ui.splash.BasicSplashHandler$AbsolutePositionProgressMonitorPart.(BasicSplashHandler.java:53)
at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:141)
at org.jkiss.dbeaver.core.application.DBeaverSplashHandler.init(DBeaverSplashHandler.java:69)
at org.eclipse.ui.internal.Workbench$2.run(Workbench.java:833)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.ui.internal.Workbench.createSplashWrapper(Workbench.java:849)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:600)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
at org.jkiss.dbeaver.core.application.DBeaverApplication.start(DBeaverApplication.java:156)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
[...]
It seems that this type of problem was solved in previous versions of DBeaver, but none of the proposed resolutions I tested worked.
Thanks,
Yves
The text was updated successfully, but these errors were encountered: