We Keep Coding

Java application startup suddenly extremely slow

Since yesterday I experience a very strange issue. I'm a dev so I already spent 12 hours solving this issue with no success prior to asking this question.
My configuration: Windows 10 Pro 64b, 1803. Latest Java 8.
Start up time of every Java application is 100x larger than the previous day. For example, "Configure Java", i.e. javacpl.exe takes 3 minutes to start, Pycharm takes 20 minutes start etc. Once started, everything works nominally. Once closed, the start up time issue repeats.
I have already reinstalled Java, even tried Java 11 to no improvement. I reinstalled all applications affected, no improvement.
During the startup, the application runs high on CPU (1 thread 100%), with no disk or network activity.
I do not think I changed anything in previous days that would affect Java. Only thing that stands out is Cumulative Windows Update 2018-11 that installed. I believe there must be other people experiencing this.
I would like to fix this without the need to reinstall Windows.

Thanks everyone for help, I ended up reinstalling Windows which solved the problem.

Java 8 Update 91 Web Start Application Has Long Startup Delay

We have a set of Java applications that we have been developing for years that are launched remotely via Web Start. After updating to Java SE 8 Update 91 there is a very significant pause (20-60 seconds depending on the application) in the startup process with no indication to the typical user that anything is happening. This pause occurs after Java's "Starting Application" dialog closes and before the application is launched.
The length of the pause appears to be correlated with the size of the application. Reverting to Java 8 Update 77 eliminates the pause altogether, and these same applications start without any pause.
Our applications do request "all-permissions" as we need to read/write data to the client's drive for caching purposes. So all of our jars are signed and have the necessary manifest modifications.
If your Java settings have the Java console enabled then the console is displayed immediately following Java's "Starting Application" dialog that appears when the application's JNLP file is accessed. However, no activity is seen in the console during this pause (for instance none of the typical Java class loading messages appear until after the pause and none of our code in the "main" method is executed until after the pause).
Some of these applications are fairly large. The code we've written is about 10-12MB, and additional resources total between 15-20MB depending on the application.
I found a JDK bug report that sounds very similar... bug report
This report states that using an older Java version results in instant startup if the Java cache is removed before the first start. The issue that I'm reporting does not seem to be impacted by the Java cache. Reverting to Java 8 Update 77 results in instant startup without deleting the Java cache.
The Java release notes for Java 8 Update 91 mention a bug fix "Regression in Applet startup time fixed". But I don't see anything that would indicate an intentional change that would result in a long pause during startup (such as increased security scanning, etc).
With this length of pause in startup and no ability to indicate to the user that something is happening we are getting complaints about the applications.
Any help would be greatly appreciated.
UPDATE July 1, 2016...
I found this SO question that seems to describe the identical symptoms: similar issue. However, it was related to Java 7 Update 40. And the resolution was to disable the revocation check in the deployment.properties file.
I have used the Java console to set "Do not check" for both "Perform signed code certificate revocation checks on" and "Perform TLS certificate revocation checks on". And I checked to make sure that the changes are reflected in the deployment.properties file. However, these setting do not fix or improve the issue at all.
If this had worked it would be a great indicator of the problem, but it would not be a useful "solution" to have clients turn off these revocation checks in their advanced settings. It especially wouldn't be helpful for the general public that have access to a number of our applications.
UPDATE July 7, 2016...
Based on the comment by jaivalis I downloaded the early access release of the Java 8 Update 112 JRE. When I run our applications with this JRE there is no pause at all. The applications run immediately after the "Starting Application" dialog closes.
So far I can't find any notes that explain why this would be. I am hoping this "fix" isn't the result of new security measures that have not been completely applied to this early access release. I'm hoping that something has actually been addressed and that the immediate launch performance will remain when this release is official.
By the way I cannot find an official release date for Java 8 Update 112. I was hoping it would happen in July, but I see some indications of October. Anyone have any information on when this update will be generally available?
Here is the early access page for Java 8 Update 112 early access
Here is the release date info I found Java 8 Update 112 release timeline
This page also mentions a Java 8 Update 102, but I can't find an early access release for that update. Any links I find point to the 112 update.

This issue has been resolved with the Java 8 update 101 release (technically build 1.8.0_101-b13).

Hello I found something that might help you :)
In the recent patch notes from Oracle it stated that this was a bug issue in the last patch of Java
Personally I would find a third-party to download a previous version of java
Here is a link to the patch notes
http://www.oracle.com/technetwork/java/javase/8u20-relnotes-2257729.html
Hope you find the issue!

Performance loss after Java upgrade to Java SE 8 Update 91

We are maintaince legacy Java system (Swing + JasperReports + MSSQL)
After Java automatically update to version 1.8.91 we got lot of troubles.
System critically lost performance.
Most problems we have with JasperCompileManager.compileReport(reportFile)
On previous Java version (Java SE 8 Update 77) middle size reports used 1-10 seconds to compile.
After upgrade to Java SE 8 Update 91 now same report using 30-170 seconds for compilation.
This effect visible better when program start through our local Java web start server.
On Java SE 8 Update 91 it really starting > 10 times slowly
Downgrade to Java SE 8 Update 77 solve problem, but this is problem for us stop upgrade on over than 4000 computers.
How is known how can fix this?

Java 6u16 stopped with no reason on Window Server 2008 R2 SP1

I have a Java application running on Window Server 2008 R2 SP1 (Under Copyright 2009) with JVM 6u16 x64, my program will write log in every 5 seconds to show it is still alive, however, the program itself has stopped writing log for 10 to 20 seconds with no reason.
I have used a VisualVM to monitor my Java application, but it stopped as well, as the VisualVm keep flooding new threads (for monitoring) during the halt period
The halt happens only between 9am to 4pm (3 to 4 times a day) but not in the night time.
This Java application works fine on another Window Server 2008 R2 SP1 (Under Copyright 2007), so I am wondering whether the new Win Server 2008 (2009 ver) has some compatibility issue with the JVM, and whether there are any KB which has fixed that
Tested 2 more things, but still no luck
1. Wrote a C++ program to write a date time log in every second, but it didn't stop writing when the JVM halt, which indicates no issues related to the OS
2. Upgrade to JVM 6u45, but the java program still paused for 1 time and last for 10 seconds, which is better than 6u16, as it happened around 3 to 4 times in day time.
Thanks for help

It sounds like you may have an issue with occasional "full GC" pauses.
I suggest you turn on GC logging, and then see if there is a correlation between these unwanted outages and the events in the GC log messages; read about the -Xloggc:file option in the Java command manual entry.
Depending on what that tells you, the solution may be to adjust your JVM's GC options.

Play! framework hangs on compile, no errors reported

Just moved my app to a new CentOS server. After fiddling for a long time, I can't play to compile or get any errors. The shell output will show me the last file compiling and then hang. I'm running the Scala 0.9.1 module.
I did a strace on the process, this is all I got. Not sure if it helps.
futex(0x410489d0, FUTEX_WAIT, 5403, NULL
Any ideas to the cause? Or where I can begin troubleshooting?
Thanks.

Googling on FUTEX_WAIT I found this mailing list thread for OpenJDK describing your problem. They advised the user to go to the distro-specific forum and ask the same question, which led me to this forum thread which is specific for Fedora 10. This seems to be a "common" problem related to some Linux distros, some JVMs and gvfs-fuse-daemon or some other process keeping locks.
No idea towards a specific solution, but I hope one of the following helps:
Read this question which deals with the same issue, only related to Citrix
This problem seems to have been around a while, so make sure you update your JVM to the latest version
Update your distro to the latest version if at all possible (especially any kernel updates, which according to this Sun bug fixed the issue)
Contact the CentOS community as this issue seems to be related to futex and Linux; they should be able to help you further
I didn't immediately come across a clear solution for this issue, so if you find one, please update this question so we can save it for future generations to come ;-)

As it turns out tmbrggmn was right and this is indeed related to the particular kernel on the machine I was using.
The particular kernel was an open source Zen kernel running CentOS and was using software virtualization. I migrated to a Citrix Kernel and now Play! compiles just fine.
A uname -a on the buggy kernel was:
Linux examplehost.com 2.6.18-274.17.1.el5xen #1 SMP Tue Jan 10 18:06:37 EST 2012 x86_64 x86_64 x86_64 GNU/Linux