Created attachment 130905 [details] full valgrind output When testing my application (https://github.com/colinkeenan/silentcast), using valgrind, I am getting numerous Invalid read and write errors whenever my application shows a window with a grid of widgets and labels. My application can only run on X11 so I chose xlib backend for reporting this bug. cairo 1.14.8 gtk3 3.22.10 Arch Linux 4.10.10-1-ARCH plasma-desktop 5.9.4 valgrind -v --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=20 --log-file=vgdump scpkg/silentcast I've attached the full output (vgdump). Here is the specific error: ==15458== 168 errors in context 1 of 66: ==15458== Invalid read of size 4 ==15458== at 0x6689F2A: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x668BADE: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x668C940: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x668D0A9: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x662E5EF: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x66A81C7: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x667A0A6: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x663769B: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x6630008: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x6628E74: cairo_fill (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x5306A27: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x5304478: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x541EDA6: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x52EA451: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x5316993: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x54FCC0A: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x52E06EF: gtk_container_propagate_draw (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x52E07D1: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x5361223: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x52E572C: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== Address 0xffeffe678 is on thread 1's stack ==15458== ==15458== ==15458== 168 errors in context 2 of 66: ==15458== Invalid write of size 4 ==15458== at 0x668C90D: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x668D0A9: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x662E5EF: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x66A81C7: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x667A0A6: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x663769B: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x6630008: ??? (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x6628E74: cairo_fill (in /usr/lib/libcairo.so.2.11400.8) ==15458== by 0x5306A27: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x5304478: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x541EDA6: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x52EA451: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x5316993: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x54FCC0A: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x52E06EF: gtk_container_propagate_draw (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x52E07D1: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x5361223: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x52E572C: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x52EA56F: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== by 0x5362300: ??? (in /usr/lib/libgtk-3.so.0.2200.10) ==15458== Address 0xffeffe678 is on thread 1's stack ==15458== ==15458== ERROR SUMMARY: 400 errors from 66 contexts (suppressed: 0 from 0) Is this a recurrence of a bug from 5 years ago?: https://bugs.freedesktop.org/show_bug.cgi?id=52548
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/cairo/cairo/issues/329.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.