# The window terminated unexpectedly (reason: ‘crashed’, code: ‘5’) - 100% reproducible with Atlassian MCP

**URL:** <https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502>\
**Category:** Bug Reports\
**Created:** [October 7, 2025, 1:47pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502 "2025-10-07T13:47:43Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pael\_Lesneu](https://avatars.discourse-cdn.com/v4/letter/p/ea666f/32.png) [@Pael\_Lesneu](https://forum.cursor.com/u/Pael_Lesneu)\
**Post date:** [October 7, 2025, 1:47pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/1 "2025-10-07T13:47:44Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

The window terminated unexpectedly (reason: ‘crashed’, code: ‘5’)  
I use Atlassian MCP. and it started to crash with this prompt: “Let’s collect Jira Custom Required Fields per ticket type.”  
Actually, it crashes for any other prompt related to Atlassian MCP, but in 5% it could work.  
I noticed that it always crashed when I see “chat summarization” message.  
Issue appeared October 6 2025, few days before it was working fine

### Steps to Reproduce

1. Install Atlassian MCP and login
2. Type in chat “Let’s collect Jira Custom Required Fields per ticket type.”

### Expected Behavior

application does not crash

### Screenshots / Screen Recordings

 ![cursor-crashed.png](https://us1.discourse-cdn.com/cursor1/original/3X/2/b/2b1114086a0323132626e6cb9ce79b441ffc3ef2.png)

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.38  
VSCode Version: 1.99.3  
Commit: fe5d1728063e86edeeda5bebd2c8e14bf4d0f960  
Date: 2025-10-06T18:18:58.523Z (19 hrs ago)  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1  
V8: 13.2.152.41-electron.0  
OS: Darwin arm64 24.6.0

### For AI issues: which model did you use?

Auto

### For AI issues: add Request ID with privacy disabled

236d9714-2b08-4999-9fdd-179fa6df240a

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [October 7, 2025, 4:15pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/2 "2025-10-07T16:15:09Z")

</div>

Hey, thanks for the report. Let me know if this happens in your other projects as well. I don’t think it’s related to the mentioned MCP server, but we’ll check.

---

<div class="post-metadata">

**Author:** ![Pael\_Lesneu](https://avatars.discourse-cdn.com/v4/letter/p/ea666f/32.png) [@Pael\_Lesneu](https://forum.cursor.com/u/Pael_Lesneu)\
**Post date:** [October 7, 2025, 6:50pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/3 "2025-10-07T18:50:21Z")

</div>

Yes, I’ve tried:

1. different project
2. copy current project to different directory
3. running with disabling extensions flag
4. clearing cache, npx cache

---

<div class="post-metadata">

**Author:** ![23942md](https://avatars.discourse-cdn.com/v4/letter/2/9dc877/32.png) [@23942md](https://forum.cursor.com/u/23942md)\
**Post date:** [October 8, 2025, 3:26am UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/4 "2025-10-08T03:26:07Z")

</div>

Atlassian’s MCP endpoint started returning 404 Missing sessionId responses.

It looks like Cursor’s renderer or MCP handler doesn’t handle the missing sessionId gracefully and throws a TypeError during normalizePath, which tears down the renderer.

---

<div class="post-metadata">

**Author:** ![Pael\_Lesneu](https://avatars.discourse-cdn.com/v4/letter/p/ea666f/32.png) [@Pael\_Lesneu](https://forum.cursor.com/u/Pael_Lesneu)\
**Post date:** [October 8, 2025, 11:29am UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/6 "2025-10-08T11:29:03Z")

</div>

Reinstalling Cursor IDE from scratch doesn’t help as well. I’m just curious if somebody else has this issue. If I should continue research if something wrong with my environment or it’s just a bug.

---

<div class="post-metadata">

**Author:** ![Privilege\_Mendes](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Privilege\_Mendes](https://forum.cursor.com/u/Privilege_Mendes)\
**Post date:** [October 9, 2025, 8:08pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/7 "2025-10-09T20:08:17Z")

</div>

I am having the exact same issue during summarization while i work with the supabase MCP. I also tried downgrading, changing models, clearing cache and even different laptops Mac M1 and M3. still same issue. its’s been 3 days now and I was hoping it was just not me..

---

<div class="post-metadata">

**Author:** ![John\_Zittlau](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@John\_Zittlau](https://forum.cursor.com/u/John_Zittlau)\
**Post date:** [October 9, 2025, 8:30pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/8 "2025-10-09T20:30:47Z")

</div>

I’m seeing the same behaviour with an MCP server I’m writing. As soon as “summarizing chat” appears, cursor crashes.

With a prompt that doesn’t require summarization, it works fine.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [October 10, 2025, 6:52am UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/9 "2025-10-10T06:52:31Z")

</div>

Thanks for the info, we’re looking into it.

---

<div class="post-metadata">

**Author:** ![john\_garrish](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@john\_garrish](https://forum.cursor.com/u/john_garrish)\
**Post date:** [October 15, 2025, 7:23pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/10 "2025-10-15T19:23:54Z")

</div>

experiencing the same issue with Atlassian MCP - crashes cursor at the end of the summarizing chat context (was the last thing I saw before the crash)

---

<div class="post-metadata">

**Author:** ![Curtis\_Janczak](https://avatars.discourse-cdn.com/v4/letter/c/c5a1d2/32.png) [@Curtis\_Janczak](https://forum.cursor.com/u/Curtis_Janczak)\
**Post date:** [October 17, 2025, 10:40pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/11 "2025-10-17T22:40:21Z")

</div>

Running into the same thing on Mac.

---

<div class="post-metadata">

**Author:** ![James\_Watts](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@James\_Watts](https://forum.cursor.com/u/James_Watts)\
**Post date:** [October 20, 2025, 1:51pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/12 "2025-10-20T13:51:46Z")

</div>

Looks like this issue was reported at 1.7.38. Just checking in to say it’s still an issue at 1.7.52.

Version: 1.7.52 (Universal)  
VSCode Version: 1.99.3  
Commit: 9675251a06b1314d50ff34b0cbe5109b78f848c0  
Date: 2025-10-17T01:41:03.967Z  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1  
V8: 13.2.152.41-electron.0  
OS: Darwin arm64 24.5.0

---

<div class="post-metadata">

**Author:** ![seso](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@seso](https://forum.cursor.com/u/seso)\
**Post date:** [October 30, 2025, 3:08pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/13 "2025-10-30T15:08:51Z")

</div>

Are there any logs one should provide to speed up the correction of this bug? Where does one find them?

---

<div class="post-metadata">

**Author:** ![Yurii\_Yurii](https://avatars.discourse-cdn.com/v4/letter/y/ea666f/32.png) [@Yurii\_Yurii](https://forum.cursor.com/u/Yurii_Yurii)\
**Post date:** [November 7, 2025, 2:27pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/14 "2025-11-07T14:27:04Z")

</div>

getting this error every time now, after updating to 2.0.64 version, I believe before it was ~1.9 (before 2.0 at all).  
I am working with devcontainers and I do have Jira MCP. Turning off of Jira MCP doesn’t help. All projects are old. Mac OS, M1

---

<div class="post-metadata">

**Author:** ![Yurii\_Yurii](https://avatars.discourse-cdn.com/v4/letter/y/ea666f/32.png) [@Yurii\_Yurii](https://forum.cursor.com/u/Yurii_Yurii)\
**Post date:** [November 7, 2025, 2:42pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/15 "2025-11-07T14:42:07Z")

</div>

here what I see in dev tools and process explorer. Nothing suspicious in PE

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/b/9/b9de784ca46c6db328d9fc5bd3095c1851cb773e.jpeg)

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [November 29, 2025, 2:43pm UTC](https://forum.cursor.com/t/the-window-terminated-unexpectedly-reason-crashed-code-5-100-reproducible-with-atlassian-mcp/136502/16 "2025-11-29T14:43:00Z")

</div>

Closed on November 29, 2025, 2:43pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
