-
Notifications
You must be signed in to change notification settings - Fork 42
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
Another small pitfall for the docs - GSlice memory error #213
Comments
That's an interesting one. I'd rather try to understand and fix it first, if there is a technical reason for why it can't be fixed I'll include a mention in the pitfalls section. Would you be willing to help me by giving more info on how to reproduce the bug with a minimal test case? If for some reason your test case is big, would you be able to run your application with |
yes sure it is better to fix it. i was not sure if it is a glib/gtk problem. |
here is one with the GSlice Error Thread 1 "node" received signal SIGABRT, Aborted. |
it happens when the mouse pointer leaves the window. may be not all cases but this i could observe multiple times. |
another observation: with G_SLICE=always-malloc set i have no sudden crashes anymore but suddenly the motion event frequency goes down to c.a 3 events per second which is either unusable. however so far i cannot see any leaks in the system monitor. |
Got it. Do you happen to have a reproducible example? If your code is in a public repo I'd be happy to test it. |
https://github.com/docb/gtkosc |
Got it. I've been able to reproduce quite quickly, I'll investigate. |
hi,
in my node-gdk app i got frequently
MEMORY-ERROR: node[112483]: GSlice: assertion failed: sinfo->n_allocated > 0
Aborted (core dumped)
Solution (due to some posts and it does so far not occur anymore):
G_SLICE=always-malloc node index.js
best, christian
The text was updated successfully, but these errors were encountered: