PyCharm crashes when creating new Python environment on Windows (JRE EXCEPTION_ACCESS_VIOLATION / verifier.cpp errors)
I am experiencing consistent crashes in PyCharm when attempting to create a new Python virtual environment on Windows. The crash occurs immediately after clicking "Create Environment" in the PyCharm interpreter setup. Reinstalling PyCharm and clearing caches did not resolve the issue.
Crash log files generated by PyCharm:
1. java_error_in_pycharm_1656.log
- EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffe1dda5fc4, pid=1656, tid=34852
- JRE version: OpenJDK Runtime Environment JBR-21.0.8+1-1038.72
- Java VM: OpenJDK 64-Bit Server VM JBR-21.0.8+1-1038.72 (mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
- Problematic frame: [jvm.dll+0x835fc4]
2. java_error_in_pycharm_19040.log
- Internal Error (verifier.cpp:2038), pid=19040, tid=18108
- guarantee(cp->cache() == nullptr) failed: not rewritten yet
- JRE version: OpenJDK Runtime Environment JBR-21.0.8+1-1038.73
- Java VM: OpenJDK 64-Bit Server VM JBR-21.0.8+1-1038.73 (mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
Environment:
- OS: Windows 10/11 (64-bit)
- PyCharm version: 2025.2.5
- JDK: Bundled JBR (OpenJDK 21.0.8+1)
- Tried deleting caches and reinstalling PyCharm, but issue persists.
Steps to reproduce:
1. Open PyCharm
2. Go to Settings > Project Interpreter
3. Click "Add Interpreter" > "New Environment"
4. PyCharm immediately crashes
Request:
Looking for guidance or a workaround. Has anyone else encountered similar crashes when creating virtual environments in PyCharm on Windows?
请先登录再写评论。
Hi there
This is not a common or known issue, It is worth checking if there is further information in the windows event logs or possibly disable any antivirus in use.
May I ask if you could give a try upgrading to PyCharm 2025.3 which is just released?
If not, would it be possible a reinstall but this time remove all remaining folders of pycharm after the uninstall as there might be corrupted files leftover.
you can find the list of folders used by pycharm here:
https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs
Kind regards,
Hi, thank you for the suggestions.
I would like to provide an update after trying your recommendations.
1. Fully removed all PyCharm folders and reinstalled
Before posting this thread, I had already tried removing all PyCharm-related folders.
This time, I repeated the process again following your link, deleting all of the following:
After completely cleaning all folders, I installed PyCharm 2025.3.
2. PyCharm 2025.3 still crashes when creating a new environment
When I launched 2025.3 for the first time, it immediately attempted to create a Python environment during initial setup.
Just like previous versions, PyCharm crashed while the environment creation was still in progress.
After reopening PyCharm, it displayed the following error:
Internal error
com.intellij.diagnostic.PluginException: Truncated class file [Plugin: com.intellij]
at com.intellij.serviceContainer.ServiceInstanceInitializer.createInstance$suspendImpl(ServiceInstanceInitializer.kt:52)
at com.intellij.serviceContainer.ServiceInstanceInitializer.createInstance(ServiceInstanceInitializer.kt)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder$initialize$1$1.invokeSuspend(LazyInstanceHolder.kt:165)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder$initialize$1$1.invoke(LazyInstanceHolder.kt)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder$initialize$1$1.invoke(LazyInstanceHolder.kt)
at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:44)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:166)
at kotlinx.coroutines.BuildersKt.withContext(Unknown Source)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder$initialize$1.invokeSuspend(LazyInstanceHolder.kt:163)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder$initialize$1.invoke(LazyInstanceHolder.kt)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder$initialize$1.invoke(LazyInstanceHolder.kt)
at kotlinx.coroutines.intrinsics.UndispatchedKt.startCoroutineUndispatched(Undispatched.kt:20)
at kotlinx.coroutines.CoroutineStart.invoke(CoroutineStart.kt:360)
at kotlinx.coroutines.AbstractCoroutine.start(AbstractCoroutine.kt:134)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch(Builders.common.kt:52)
at kotlinx.coroutines.BuildersKt.launch(Unknown Source)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder.initialize(LazyInstanceHolder.kt:148)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder.access$initialize(LazyInstanceHolder.kt:15)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder.tryInitialize(LazyInstanceHolder.kt:138)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder.getInstance(LazyInstanceHolder.kt:96)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder.getInstance$suspendImpl(LazyInstanceHolder.kt:84)
at com.intellij.platform.instanceContainer.internal.LazyInstanceHolder.getInstance(LazyInstanceHolder.kt)
at com.intellij.platform.instanceContainer.internal.InstanceContainerImpl.instance(InstanceContainerImpl.kt:68)
at com.intellij.serviceContainer.ComponentManagerImpl.getServiceAsync(ComponentManagerImpl.kt:661)
at com.intellij.openapi.progress.impl.TaskInfoEntityCollectorKt$collectActiveTasks$1.invokeSuspend(TaskInfoEntityCollector.kt:152)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:610)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runDefaultDispatcherTask(CoroutineScheduler.kt:1194)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:906)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:775)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:762)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [Kernel@3cvj5pc2f4652c0hgmvs, Rete(abortOnError=false, commands=capacity=2147483647,data=[], reteState=kotlinx.coroutines.flow.StateFlowImpl@15d0c81b, dbSource=ReteDbSource(reteState=kotlinx.coroutines.flow.StateFlowImpl@15d0c81b)), DbSourceContextElement(kernel Kernel@3cvj5pc2f4652c0hgmvs), ComponentManager(ApplicationImpl@1425670210), com.intellij.codeWithMe.ClientIdContextElementPrecursor@5d940b45, CoroutineName(com.intellij.openapi.progress.impl.TaskInfoEntityCollector), StandaloneCoroutine{Cancelled}@7719b66a, Dispatchers.Default]
Caused by: java.lang.ClassFormatError: Truncated class file
at java.base/java.lang.ClassLoader.defineClass2(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1118)
at com.intellij.util.lang.UrlClassLoader.consumeClassData(UrlClassLoader.java:332)
at com.intellij.util.lang.ZipResourceFile.findClass(ZipResourceFile.java:114)
at com.intellij.util.lang.JarLoader.findClass(JarLoader.java:60)
at com.intellij.util.lang.ClassPath.findClassInLoader(ClassPath.java:290)
at com.intellij.util.lang.ClassPath.findClass(ClassPath.java:240)
at com.intellij.util.lang.UrlClassLoader.findClass(UrlClassLoader.java:253)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:593)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
at com.intellij.openapi.project.impl.ProjectManagerImpl.<init>(ProjectManagerImpl.kt:138)
at com.intellij.platform.instanceContainer.instantiation.InstantiateKt.instantiate$lambda$0(instantiate.kt:42)
at com.intellij.platform.instanceContainer.instantiation.InstantiateKt.instantiate$lambda$3$0(instantiate.kt:288)
at com.intellij.platform.instanceContainer.instantiation.InstantiateKt.withStoredTemporaryContext(instantiate.kt:304)
at com.intellij.platform.instanceContainer.instantiation.InstantiateKt.instantiate(instantiate.kt:287)
at com.intellij.platform.instanceContainer.instantiation.InstantiateKt.instantiate(instantiate.kt:39)
at com.intellij.serviceContainer.ServiceInstanceInitializer.createInstance$suspendImpl(ServiceInstanceInitializer.kt:29)
... 31 more
-----
JRE: 21.0.8+9-b1163.69 amd64 (JetBrains s.r.o.)
E:\Soft\Pycharm\PyCharm 2025.3\jbr
3. A new crash log was generated
After the crash, PyCharm created a new file:
java_error_in_pycharm_21368.log
Its content begins with:
## A fatal error has been detected by the Java Runtime Environment:## EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000000000002, pid=21368, tid=30184## JRE version: OpenJDK Runtime Environment JBR-21.0.8+9-1163.69-jcef (21.0.8+9) (build 21.0.8+9-b1163.69)# Java VM: OpenJDK 64-Bit Server VM JBR-21.0.8+9-1163.69-jcef (21.0.8+9-b1163.69, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)# Problematic frame:# V [jvm.dll+0x372592]## No core dump will be written. Minidumps are not enabled by default on client versions of Windows## If you would like to submit a bug report, please visit:# https://youtrack.jetbrains.com/issues/JBR#I noticed that every crash generates a new java_error_in_pycharm_xxx.log, and the
EXCEPTION_ACCESS_VIOLATIONsection differs each time (different pc/pid/tid and problematic frame).4. Summary
Even after:
PyCharm still crashes during environment creation and continues producing new JVM fatal error logs.
Thank you for your help.
I have crated an internal case to follow up on this with our JBR team
https://youtrack.jetbrains.com/issue/JBR-9774/PyCharm-Crashes-EXCEPTIONACCESSVIOLATION-when-creating-new-Python-environment
Please feel free to follow/comment directly there as well.
Kind regards,
Would you please attach in the youtrack case the full java error logs (such as java_error_in_pycharm_xxxx.log) for our team to analyse?
Kind regards,
Hi there,
Thank you for creating the internal case to track this issue. I have attached the requested log files to the YouTrack case as mentioned.
I appreciate your team’s support.
Kind regards,
Thank you
Our JBR team has provided some advice on next steps so let us follow up this case investigation in youtrack.
Kind regards,