# An excessive number of EA connections causes slowness in the system and high RAM usage

### Description

* Too many open connections observed when OpsHubEAWindowsService is running as console application and OpsHubEAWindowsService is forced closed using cancel button.
* Observations:
  * High RAM consumption
  * Slowness in the system because of too many EA connections remaining open.

### Cause

* This happens when the OpsHubEAWindowsService is being launched via console application and it has been forcibly closed using the cancel button.

### Solution

* Stop the OpsHubEAWindowsService (Recommend to close by pressing enter key).
* Press Windows + R to open the Run Dialog.
* Type 'taskmgr' and click OK to open Task Manager.

<div align="center"><img src="https://3296007024-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpHalzzeQCgmjCxMGg14%2Fuploads%2Fgit-blob-1c0e6089cfa3f89bce7c074b2a05ea13e2d8630e%2FTaskManager.png?alt=media" alt="" width="800"></div>

* In the 'Background processes' section locate 'Enterprise Architect - UML Development Tool' processes.
* Right click on each process and select 'End task' to terminate it and release the resource.

<div align="center"><img src="https://3296007024-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpHalzzeQCgmjCxMGg14%2Fuploads%2Fgit-blob-a0bd70352d1ea1c10a2fa201fedf0afbb2e128ef%2FEnd-Process.png?alt=media" alt="" width="900"></div>

> **Note**: To release all the connections properly when closing OpsHubEAWindowsService, we recommend to close OpsHubEAWindowsService using Enter key. Refer to [Setting up OpsHubEAWindowsService](https://docs.opshub.com/connectors/enterprise-architect#setting-up-opshubeawindowsservice)
