# Bug OP-9505 - Memory leak in work package split screen

Project: OpenProject
Status: on hold
URL: https://community.openproject.org/work_packages/OP-9505

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module | Modules and project features / Work packages |
| Target versions |  |
| Observed in versions | 11.4.0 |
| Sprint |  |
| Backlog bucket |  |
| Bug found in version (deprecated) | 11.4.x |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### **Environment**:

OP: 11.4+

### **Logs**

The browser's task manager with "JavaScript Memory" selected.

### **Steps to reproduce:**

1.  Go to a work package list
2.  Open the split screen
3.  Switch back and forth between one work package and the other
    1.  This seems to have the most effect with a lot of (which exactly is unknown):
        1.  Custom fields
        2.  Inline tables
        3.  Custom actions
4.  See JavaScript Memory footprint

### **Actual Behavior**

The memory consumption by JavaScript rises continuously and the memory is never released. This results in the browser becoming slower and slower over time. Eventually the browser tab will crash.

### **Expected Behavior**

Memory being released at appropriate times. No crashes and no performance degradation.

### Workarounds

  - Memory is feed by leaving the page:
      - Going to a different place within the application (e.g. wiki, start page, ...)
      - Reloading the page via the browser
