-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xydisplay makes max crash (memory leaks ?) #141
Comments
further analysis on windows : If you open the .dmp file in the crash folders and ask Windbg to open it and analyze it, I have those results: CONTEXT: (.ecxr) EXCEPTION_RECORD: (.exr -1) PROCESS_NAME: Ableton Live 11 Standard.exe READ_ADDRESS: ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%p emploie l'adresse m moire 0x%p. L' tat de la m moire ne peut pas tre %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff STACK_TEXT:
|
after several minutes of intensive use of xydisplay on a mac, max crashes and leaved the attached report
bug_report_ness.txt
I'm not a developer, so according to chatGPT (this is not serious isn't it ?):
"The stack trace shows that the crash occurred while trying to paint a component in the application. The crash was caused by a pointer authentication failure, which could indicate a memory issue."
the xy_paint is cited in the report (line 9 of thread 0) and here are some clues given by chatGPT also :
"One thing to note is that the code uses a hash table to store points, which can be a potential source of memory leaks if the hash table is not properly managed. The t_point struct has a next and prev pointer which suggests that it is used in a linked list. If a point is removed from the linked list but not removed from the hash table, it will cause a memory leak.
It's also important to check if all allocated memory is properly freed in the xy_free function."
Hope this helps
Damien
The text was updated successfully, but these errors were encountered: