Skip to content
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

pango crash by "object allocation during garbage collection phase" #1231

Closed
tsutsui opened this issue Jul 3, 2018 · 4 comments

Comments

@tsutsui
Copy link

commented Jul 3, 2018

As noted in #1230, ruby-gnome2 3.2.7 + 8816bbd change triggers coredump of ruby which runs mikutter 3.7.2. The crash seems to happen on drawing tweet by pango and cairo.

A crash log and gdb trace (no debug info) are attached.
mikutter-crash-log.txt
mikutter-crash-gdb-trace.txt

@tsutsui

This comment has been minimized.

Copy link
Author

commented Jul 3, 2018

gdb trace with glib2 gem built with --enable-debug-build:
mikutter-crash-gdb-trace-enable-debug-build.txt

@kou kou closed this in ec4160b Jul 4, 2018
@kou

This comment has been minimized.

Copy link
Member

commented Jul 4, 2018

Thanks.
I've fixed it by ec4160b. Can you try it?

@tsutsui

This comment has been minimized.

Copy link
Author

commented Jul 4, 2018

The assertion no longer happens and the memory leak reported in #1230 seems also fixed (sometimes VSZ decreases so GC looks working as expected). Thanks.

@kou

This comment has been minimized.

Copy link
Member

commented Jul 5, 2018

Yay!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.