UnsatisfiedLinkError of swt-win32-4965r8.dll on Windows Server 2008 R2

[serjiokov]

Hello,

Issue description:

Recently we switched to the latest Eclipse SDK release
https://download.eclipse.org/releases/2024-06 version build 202405031000
and bumped with product crash on specific OS's: Windows 8 / Windows Server 2008
due to UnsatisfiedLinkError of swt-win32-4965r8.dll

PS:
Let us please, know if you reduce support of OS like Windows 8 / Windows 2008 RC

The original issue in DBeaver product:
dbeaver/dbeaver#34034

[HeikoKlare]

Could you please detail from which Eclipse version you switched to the new one?

I am not aware of very recent changes that (explicitly) reduced support for older Windows version. But note that, if I am not mistaken, the Windows versions you mention are out of support for quite some time, so

1. probably no one (explicitly) considers compatibility with such versions when making changes to SWT, and
2. functionality specific for these old version has already been reduced over the last years with changes like in [win32] Fix various warnings in native libs, treat any new warnings as errors #370, precisely 3cc6898

[serjiokov]

Thanks for your response.

[serjiokov]

Hello,
we switched from
2024-06/202404121000/
to
2024-06/202405031000/

The entire support of Windows 7, Windows 8, Windows Server 2008 R2, MacOS Catalina 10.15.7
is broken due to

Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: 
	D:\bin\dbeaver\home\swt-win32-4965r8.dll: Belirtilen yordam bulunamadı
	no swt-win32 in java.library.path:

References issues
dbeaver/dbeaver#34244
dbeaver/dbeaver#34197
dbeaver/dbeaver#34034
dbeaver/dbeaver#30700

Could you please confirm that Windows 7, Windows 8, Windows Server 2008 R2, MacOS Catalina 10.15.7
out of support?

[HeikoKlare]

I am not aware of any changes in that date range that have actively removed support for those operating systems. We had additions in the Windows native bindings (94d9c5b), which might be a reason for outdated Windows versions not to work (properly) anymore, as these Windows version may not provide the accessed methods. But I am not sure whether that's really the root cause here as, first, I think there are also other OS methods not provided by older Windows versions which do not make the SWT DLLs loading fail and, second, I do not see changes to MacOS in SWT, but you say that MacOS is also not working anymore.

In dbeaver/dbeaver#34244 (comment), this error message is posted, which actually sounds like missing methods provided by the OS:

java.lang.UnsatisfiedLinkError: Could not load SWT library. 
Reasons: 
	C:\Users\***\AppData\Local\DBeaver\swt-win32-4965r8.dll: The specified procedure could not be found
	no swt-win32 in java.library.path: 

But this does still not explain problems with MacOS.

[serjiokov]

One point,
The users who are using Oses below ( Windows 7, 8, 2008 ) will bumped with the same set issue UnsatisfiedLinkError after switching to Eclipse release 2024-06, it not to be so friendly for them. Could you please investigate it?

[HeikoKlare]

I understand that this is annoying and of course it would be great to have some tracking of minimal system requirements and some validation on startup and update whether they are fulfilled. We had a similar discussion in eclipse-platform/.github#193.

Could you please investigate it?

The problem is: Who do you mean by "you"? Eclipse is a community project, so it up to its users to implement fixes and required features. I (personally) cannot do that, since this is not an issue for me and my company, as users of our products do not use outdated Windows versions. And independent from what my company needs directly, I am sorry to say that there are far more important things for the Eclipse platform to be done than supporting outdated operating systems or handling that someone uses them. Note that this is not about dropping support for like a two-year-old OS, but for OS versions have been out-of-support for some time anyway. If it is important for you to have that feature, it would be great if you could contribute that to the Eclipse platform.

[greenozon]

this is critical issue, hit it as well recently, please do not drop support of big list of Windows OSes like 7, etc

details:

	C:\Users\User\.swt\lib\win32\x86_64\swt-win32-4965r11.dll: The specified procedure could not be found
	Can't load library: C:\Users\User\.swt\lib\win32\x86_64\swt-win32.dll
	Can't load library: C:\Users\User\.swt\lib\win32\x86_64\swt.dll
	C:\Users\User\.swt\lib\win32\x86_64\swt-win32-4965r11.dll: The specified procedure could not be found

	at org.eclipse.swt.internal.Library.loadLibrary(Library.java:345)
	at org.eclipse.swt.internal.Library.loadLibrary(Library.java:254)
	at org.eclipse.swt.internal.C.<clinit>(C.java:19)
	at org.eclipse.swt.internal.win32.STARTUPINFO.<clinit>(STARTUPINFO.java:42)
	at org.eclipse.swt.widgets.Display.<clinit>(Display.java:149)
	at com.pnfsoftware.jeb.rcpclient.extensions.app.App.onPreDisplayCreation(App.java:93)
	at com.pnfsoftware.jeb.rcpclient.JebApp.onPreDisplayCreation(JebApp.java:52)
	at com.pnfsoftware.jeb.rcpclient.extensions.app.App.<init>(App.java:70)
	at com.pnfsoftware.jeb.rcpclient.JebApp.<init>(JebApp.java:37)
	at com.pnfsoftware.jeb.rcpclient.Launcher.main(Launcher.java:18)

[Phillipus]

I am not aware of any changes in that date range that have actively removed support for those operating systems. We had additions in the Windows native bindings (94d9c5b), which might be a reason for outdated Windows versions not to work (properly) anymore, as these Windows version may not provide the accessed methods.

That commit references SystemParametersInfoForDpi. See https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-systemparametersinfofordpi

And f809372 references GetSystemMetricsForDpi. See https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getsystemmetricsfordpi

Both of these functions require a minimum version of Windows 10:

Minimum supported client 	Windows 10, version 1607 [desktop apps only]
Minimum supported server 	Windows Server 2016 [desktop apps only]

But this does still not explain problems with MacOS.

That'll be eclipse-equinox/equinox@69b907e

please do not drop support of big list of Windows OSes like 7, etc

But these are outdated OS's and in order to progress Eclipse has to move on. And, in fact, these minimum versions are already documented. See here where it states:

Eclipse 4.32 is tested and validated on the following reference platforms (this list is updated over the course of the release cycle):

Operating System	Version	Hardware
Windows	10 11	x86 64-bit
Apple macOS	12 13	x86 64-bit

(In practice the minimum macOS is 11).

As far as I can see it would require too many reverts of code to go back. For example this commit and this one.

I'd say that ship has sailed.

[Phillipus]

I am not aware of any changes in that date range that have actively removed support for those operating systems.

My curiosity was such that I installed Windows 8 in a VM and bisected where things stopped working. Specifically, it was the new v4965r7 binaries at commit 3d87b22. This is where the new Windows OS native functions appear that were committed in 94d9c5b and f809372. But, as I said above, I doubt this will be reverted.

[HannesWell]

I am not aware of any changes in that date range that have actively removed support for those operating systems.

My curiosity was such that I installed Windows 8 in a VM and bisected where things stopped working.

Thank you for verifying!

this is critical issue, hit it as well recently, please do not drop support of big list of Windows OSes like 7, etc

I understand this is unpleasant for you, but without someone dedicated to it, it's not really feasible to provide support for a longer time than the OS vendor. And the mentioned changes really improve the situation for recent OS versions.

Of course you can still use older releases from the corresponding p2 update site or package for 2024-03 or ealier

• https://download.eclipse.org/releases/
• https://www.eclipse.org/downloads/packages/release

I'd say that ship has sailed.

I think so as well, therefore let's close this as not planned. If someone steps up to contribute fixes for the affected OS versions without affecting recent ones, we can re-open this and discuss it again.