Crash when trying to add behavior

[MathewSchaeffer]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

After importing or creating an extension/behavior, when trying to add a behavior to an object, there is a crash. See pictures below:

After some time, the error might go away and let you proceed as normal, or sometimes a restart of GDevelop is required.

Steps to reproduce

Import or create a new behavior
Select an object from the object panel - right click, add behavior
Crash happens

GDevelop platform

Desktop

GDevelop version

5.4.217

Platform info

Windows 11 64 Bit

Additional context

No response

[AnseloOriginal]

Looks like something that has to do with memory running out or write to disk restrictions. I had these kind of problems while working on a low-end pc with little ram and 28gb ssd rom

[MathewSchaeffer]

The PC I'm using has 512 GB SSD with 100 GB spare and 16 gig of ram.

[AnseloOriginal]

The PC I'm using has 512 GB SSD with 100 GB spare and 16 gig of ram.

A PC with these specs shouldn’t typically behave this way. I wasn't able to replicate the problem, which suggests it might be related to a read/write restriction on your disk or something else. Could it be caused by any app you've recently installed, or did it start after the last update? Here are a few potential fixes:

1. Move GDevelop’s Cache Folder: Try moving the GDevelop save folder (C:\Users*Your User*\AppData\Roaming\GDevelop 5) to another location to clear the cache. If this resolves the issue, delete the old one. If not, you can restore the folder to its original location.

2. Check Project Folder Permissions: Make sure the folder where you’re saving your project isn’t write-protected.

3. Restart or Reinstall GDevelop: Sometimes, a fresh start can resolve issues caused by corrupt files or settings.

[ClementPasteau]

Hi @MathewSchaeffer thanks for reporting.

@AnseloOriginal This error doesn't come from memory running our or disk restrictions, it's related to the C++ part of GDevelop trying to access an item that is not accessible anymore. So it's a bug on GDevelop's side regarding memory & object management.

Unfortunately, the root of the issue is hard to pinpoint, as this kind of errors is just a consequence of a misuse of memory that may have happened in a complete different place in the app.

I cannot reproduce the issue when following your steps. Are you having this bug, following those steps, even after restarting GDevelop?
If so let us know (and a video would help)

[AnseloOriginal]

@ClementPasteau Thanks for letting me know. Is there any way to avoid this?

[ClementPasteau]

We need to be able to reproduce it consistently so we can find the cause