Manage desktop backgrounds when running in wayland

[lukefromdc]

Set the background when in wayland using a cssprovider Read the bg image filename from and save it to gsettings Listen for the bg image filename changing Works from caja's "Change Desktop Background" menu item, from caja-extensions "set as wallpaper" and with changing the background in dconf-editor.

[lukefromdc]

This gives us background management from caja and from the wallpaper caja extension (w no changes required there). starts almost instantly with caja so no more one second of showing the wrong background at startup in a wayland session.

Note that since we are not using mate-settings-daemon (an xsettings manager) while running in wayland, we cannot use the appearance capplet in mate-control-center to set the background.

A new capplet preferably shown only in wayland would be needed, as we could not get to the background page of the appearance capplet when it won't start. Making it run in wayland would mostly overlap functions taken over by the compositor in wayland: setting gtk themes, icon themes, fonts etc..

The rest of the ways to set an image background work, though GTK only supports a few ways of rendering an image background: fill, tile, or (with no-repeat) show at original size. A color background can be obtained by using a blank image and setting it as the background in the compositor w/o a background plugin. This could later be added to caja along with gradients, but this gives us what most people use working from inside Caja. Notably, this allows a distro (or MATE itself) to use the same default background in x11 and wayland so long as it is an image (say, from mate-backgrounds).

This is part of ongoing work to allow a user to install wayfire, MATE with wayland enabled, and mate-wayland-session, then run the session from the display manager without having to configure anything before getting to work. Same new user experience on first run as x11 is the objective here or as close as we can get to it given wayland's differences and limitations.

[lukefromdc]

Note that when running something like conky that seems to only be able to draw on the compositor's background right now, using a fully transparent (0,0,0,0) background image will let the compositor's background and anything drawn on it show through, and in x11 will show the default background colors for MATE. You can still change the desktop background from caja but doing so will cover up conky (or anything else behaving this way) the first time the background is clicked on.

[lukefromdc]

Force-pushed with memory leak fixes, see above

[zhuyaliang]

I have a few suggestions here

1. background_settings = g_settings_new ("org.mate.background"); should be in fm_desktop_icon_view_init and global variables background_settings should not be used

[lukefromdc]

Last two changes refactor a bit: In wayland we now include the gsettings variable in desktop_icon_view->priv so we can work with it without declaring a global variable. Also, since most of the wayland code is now behind wayland-only build selectors, we move the last wayland-only block behind them too, so this is consistant throughout the entire file and none of the wayland code is built in x11-only builds. Both wayland and x11-only builds completed, tested to ensure no issues with the build time selectors

[lukefromdc]

Hoping I can get one more review on this

[lukefromdc]

I found the background image was being leaked on changing backgrounds, just force-pushed a fix that worked in testing here. I was able to restart caja in wayland and monitor RAM use in mate-system-monitor while changing backgrounds. Instead of ballooning like before, it went up slightly with a larger background image and returned to its previous value on switching back to the smaller filesize background image. This could be repeated many times without memory use visibly rising. Test images were an 8K and an 8M image to make it easy to see.

We attach the GtkStyleProvider to desktop_icon_view->priv so we can find it again on a background change On changing backgrounds, we remove the provider, hard free it with g_free() to unload the old background image, then initialize it anew and reload it with the new data Re-using the variable is safe according to https://stackoverflow.com/questions/504948/is-it-safe-to-reuse-pointers-variables-after-freeing-what-they-point-to g_free() is nullsafe according to https://docs.gtk.org/glib/func.free.html and in testing I got no issues from this usage.

If a more elegant approach exists I am most certainly open to it

[lukefromdc]

Still hunting the memory leak. It does NOT appear to come from the style provider as disabling loading it does not affect the memory leak. The fix I tried last night appeared to work-but only because it was crashing caja (which restarts in the wayland session as in the MATE x11 session) and I was looking at the RAM consumption in mate-system-monitor and didn't catch it right away.

Still trying to track it down, it seems that changing the gsettings value is somehow enough to increase RAM use even if caja is set to ignore the change entirely. Thus the WIP on this until I find the culprit or someone else does.

Note that caja uses about twice as much RAM to start up in wayland as it does in IceWM on x11 (used to allow running from terminal)

[lukefromdc]

latest force-push restores the mode of operation prior to my first attempt to fix the memory leak, but keeps the provider as part of the desktop-icon-view and adds it only once.

[lukefromdc]

I managed to get eel to draw the desktop background (and thus support ALL our background options) by using an existing drawing function in caja-icon-container.c that normally is excluded from the desktop. The value of this is by drawing on the icon container like a background in a navigation window, we bypass the no root window in wayland issue.

Both RAM consumption and memory leakage are greatly reduced, though about 30MB is still leaked on a change of desktop I am pretty sure that is coming from existing code somehow, especially given it is the same whether using the dialog from the desktop right-click menu, the wallpaper extension, or dconf-editor to change the image. The background is actually being set by existing code in eel-background.c so the leak is probably there in existing code. This is part of a more general excess RAM usabe in Wayland, about double that we use in X11 and calling for a general cleanup if this is even possible with such an old and complex codebase.

Still a WIP as I think I might be able to either copy in the interface used in mate-appearance-properties or if that fails write another interface to handle color and gradient as well as image background setting. These all work and fade does too from dconf-editor, and the fading works no matter how the background is changed.

[lukefromdc]

The background changing dialog now works quite well, and all background options supported in x11 from the x11 dialog are supported from the new dialog for wayland background changes, save that a cache of previous backgrounds is not kept as I was not able to figure out that part of the code. Even fading between backgrounds works. No changes for x11 as usual.

This is the "Change Desktop Background" UI as it stands now. Both image and color/gradient backgrounds are previewed.

By calling eel_background_draw () on the results of gtk_widget_get_toplevel() called on the desktop icon container we avoid the root window image so the whole MATE background handling system works.

[lukefromdc]

Final force-push corked up the memory leak: we useset_root_surface () in eel-background.c to call mate_bg_create_surface() when we set up the background or change it in x11. This works in the x11 composited case as the code in mate-desktop/libmate-desktop/mate-bg.c called by this replaces this surface with the root window, presumably freeing the original surface somewhere. When we cannot use the root window or don't have one, we create this surface over and over again with the previous code.

What I changed was to check for an already existing surface before creating a new one, and keep this change out of x11 for now just in case. Now I can change the desktop background over and over again, and RAM use stayed within a couple MB of the starting point. There could well be small memory leaks elsewhere anywhere in caja affecting this but the 32 MB (8MP image for 4K desktop at 24 bit depth) is gone. Caja stayed around 185MB for the whole string of background changes in testing this, with both images and colors.

Changing the background on x11 with a noncompositing WM may leak memory too, I will check for that and I find background changes on x11 with noncomposited marco leaking memory this can be changed in a later PR to cork it up for x11 too by removing the or x11 conditional.

Also note caja -c finished clean in a wayland session with all of this applied

[lukefromdc]

Revised the dialog to make the interface more intuitive, placing the "Image" label and the filepicker to the left of the style label and combobox, and the "Colors" label left of the color background style selector combobox, right under the "Image" label. Here it is in Menta:

And in my own theme as used in developing it:

[raveit65]

Is this ready for testing now or is it still a draft?

[lukefromdc]

Build warnings fixed, ready for testing

[zhuyaliang]

There are a large number of memory leaks in the code, my suggestion is to reduce the use of global variables

[lukefromdc]

There is no easy way to avoid globals for this, other than binding all of them into a single struct. You cannot pass two variables in a single gsettings callback, and the only way I know of to react to a button press orcombobox return is by a callback.

If there are still memory leaks they will need to be found and corked up individually, will look at each variable one at a time.

[lukefromdc]

With considerable refactoring I was able get rid of all but one of the globals, the gsettings object used everywhere in the dialog. Did have to use some static variables so we would not be remaking them every time the preview updates as users tweak settings in the dialog before closing it. Some obvious memory leaks corked in this work.

I got it to the point that I could open and close the dialog and play with it while monitoring RAM usabe by the MB and seeing a return to previous use at that resolution after ten iterations of that.

Final touches were to fix a logic error in an earlier change in eel-background.c in wayland detection, though that code won't be reached in wayland anyway this makes it more robust. Also to preview images in their original aspect ratio rather than stretched to the desktop dimension.

[lukefromdc]

Some valgrind results:

I just fired up caja with this applied under valgrind, using valgrind -s --leak-check=full caja --force-desktop

Changing backgrounds repeatedly (using both image and color backgrounds) while caja was running didn't generate any additional text in the terminal with the current code. On running caja --quit to shut it down with one navigation window having opened and been closed, I got the leak summary for the entire run, lots of problems elsewhere in caja including lots of font stuff, the sidebar, the pathbar, you name it. What I did not see was any references whatsoever to the new background handling code, though the first part of the valgrind data shown on running caja --quit would not fit in the terminal's back buffer. I ran caja --quit just after changing backgrounds though to push any data from it to the bottom of the terminal text, and got nothing from that part of the code.

==132458== LEAK SUMMARY:
==132458==    definitely lost: 44,447 bytes in 104 blocks
==132458==    indirectly lost: 165,485 bytes in 5,098 blocks
==132458==      possibly lost: 22,941 bytes in 340 blocks
==132458==    still reachable: 11,798,912 bytes in 71,083 blocks
==132458==         suppressed: 0 bytes in 0 blocks

Caja (at least under wayland) leaks memory on closing navigation windows, possibly the desktop as well as it too is a main window though a spatial window. EDIT: CONFIRMED that is related to the (caja:136770): Gtk-CRITICAL **: 16:24:27.324: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed as in valgrind caja-application (not affected by this PR) line 438 is g_list_foreach (windows, (GFunc) gtk_widget_destroy, NULL); errors that show up always under wayland and often under x11 too on closing a window That of course is a matter for another PR

[lukefromdc]

Last change ensures we only add the style provider once. It's declared as static GtkCssProvider *provider; to keep it around for each time the preview changes and it has to be reloaded. Static variables load into RAM once and are freed when the whole program is closed. Unlike globals they don't use up the namespace for functions in other files and are less likely to get stepped on by an unrelated function as a result.

As always, open to any better ideas. I just want this to work as well as possible and be maintainable going forward.

[lukefromdc]

Ran cppcheck-gui on fm-desktop-wayland-bg-dialog.c found two issues: a variable with too big a scope, and another read from gsettings before being read from the color style combobox. Latter was a cut and paste error from moving all this code around in getting rid of most of the globals, but both are now fixed.

[raveit65]

How can i select wayland-background-dialog? Edit: Got it, it's in desktop context menu

[raveit65]

With a first test selecting and switching images works well. There are a few backgrounds which takes a long time to select or switching options (strech,zoom,etc). Is it possible that only one monitor is supported? Currently i am testing my UHD wallpaper slideshow. Anyway, it's late, i need to play around more. Sadly, the caja window can't be moved. It would be easier to test wayland-desktop during normal work time.

[lukefromdc]

Try it in one monitor, it should work at normal speed. I am away from home this week, brought my desktop but only one monitor. Might be able to try a two monitor test with the laptop though. Also try with fade turned on and off, fade works same as x11 in my tests. If two monitors is slower than an x11 fade I need to look at monitor finding code and look for any loops or hangups in it.

Also how big is the largest background in MB, and how much total resolution are you applying it too?

I have made exactly zero headway in finding out why CSD prevents caja navigation windows from being moved. Must be something special about it but I have no leads at all on what it is. That's why for mate-wayland-session I have the config file set to default to SSD for wayfire. Then we can move the navigation windows.

The CSD option can follow the window decoration theme by using what we wrote to cover CSD apps in the themes, but to use it requires finding out what the hell is going on with navigation windows (and non-desktop spatial windows). That problem appeared not only in wayfire but also in Sway (when launched as a floating window), Mir, and everything I tested, I think even in GNOME (without the desktop which requires gtk-layer-shell of course).

[raveit65]

.........That's why for mate-wayland-session I have the config file set to default to SSD for wayfire. Then we can move the navigation windows.

Good, np, i will take a look at the file to see how to set caja as SSD window.

[lukefromdc]

in your wayfire.ini file, replace preferred_decoration_mode = client with preferred_decoration_mode = server This will set up ssd on all windows save CSD-only apps such as Gedit (my usual test app for this)

[lukefromdc]

At home with both monitors connected I have not had problems with Caja but I have NOT tested Caja rendering the background with two monitors yet. It may have looked right only because the compositor was handling the background. I tried to get the laptop to work for this test, but it refused to recognize the single 4K monitor I bought with me on this road trip. Somehow I didn't think to try this PR with two monitors before heading out for a ten day road trip. I do have the desktop and can work on code here though.

Test for multimonitor support is simple though: Caja will show the icons on the same monitor it is started from if started from terminal, and monitor 0 (should be leftmost) if starting with the session. Set a background for wayfire different from what you are using in Caja. If the secondary monitor shows the compositor background, multimonitor background rendering is not supported yet, same as putting icons on more than one monitor in wayland. If it shows the Caja background (chosen to be different than the compositor background), than we have working multimonitor background management.

If just a few files are slow to switch to, compare the times for switching to them in X11. If they are slow there too that's the problem. If not, I have a suspicion of what the problem is and you should be able to test the fix.

The only difference in the codepath for actually showing the background is we use the icon container to get the toplevel and put the background on the desktop window instead of the root window, which is x11-only. Since we don't have a primary monitor in Wayland save come compositor-specific implementations, it's possible my code using gkd_display_get_default() is hanging on the multimonitor case, but that should cause a crash if that is so.

At any rate, its trivial to switch that to getting the screen's display, which is always valid. If we don't have multimonitor background management though, that is not trival to fix as it requires getting each GdkMonitor (corrosponding to a physical monitor) and managing it separately. That would make all of them available to show icons-and without the x11 problem of dead space with dissimilar monitors. This would be complex and the subject of another PR., and if it worked backporting it to x11 would fix that dead space issue.

The root SURFACE in wayland is not considered a window, might only available to the compositor but Conky with wayland output does render UNDER caja's desktop once the desktop has been clicked on. Not sure if Conky is also claiming the always on the bottom position and getting it, or their devs managed to draw on that root surface. No effect from using "own window" option or not in wayland so for now conky gets exiled to xwayland to stay above caja.

[raveit65]

Ok, caja do only handle the main desktop/monitor. I did some more testing today. The delay was caused bei a 9,4 MiB png wallpaper. It seems that using huge png wallpapers are slow down switching backgrounds. Other formats like jpg, webp, svg are working well. Also our Elephants_5640x3172.jpg (15,6 MiB) doesn't cause a delay. My wallpaper slideshow (*.xml) with hidpi wallpapers runs well. Memory handling is OK. I didn't noticed any increasing memory consumption. So i think it looks good.

[raveit65]

in your wayfire.ini file, replace preferred_decoration_mode = client with preferred_decoration_mode = server This will set up ssd on all windows save CSD-only apps such as Gedit (my usual test app for this)

This works, but the decoration looks so ugly with bright menta gtk theme. Not really usable for me. Only an idea, maybe the issue with caja csd window is caused by the desktop window which has a fixed size and can't be moved?

[lukefromdc]

I should be able to re-theme the default SSD window decoration to look as much like Menta's window decoration as the default window decorator can manage, and include that in the SED runs that create a user's initial ~/config/mate/wayfire.ini

Also I recall the problem moving CSD caja navigation windows showed up as soon as I had navigation windows working in native Wayland, without having a working desktop at that time. I wish we had more eyes looking at that one, I've been trying to find it for months with no results. Nemo works, but I have no idea which of the myriad changes since Nautilus 3.0 or Nemo's first version are why.

[lukefromdc]

SHIT-that should have been a squash and merge. Cleaning that now would require locally squashing the branch, restoring from the local branch, and an ugly force-push to master that should always be avoided except in emergencies.

[lukefromdc]

As it stands the commit history looks like this:

wayland-background-dialog: fix two issues found by cppcheck

wayland-background-dialog: ensure style provider is added only once
eel-background: fix logic error in x11/wayland detection
wayland-background-dialog: Preview images at original aspect ratio
wayland-background-dialog: fix memory leaks
wayland background dialog: fix build warning
Make wayland background dialog more intuitive
Manage desktop backgrounds when running in wayland

I've seen many commit strings like this in many git histories including that of GNOME prior to Gnome 3 and during that transition.

[raveit65]

Keep commit history like it is, no need to revert it, ihmo.

[lukefromdc]

At the merge we got travis failures not caused by these commits but rather by a docker issue, same in both Debian and Fedora:

The command "./docker-build --name ${DISTRO} --config .build.yml --install" failed and exited with 1 during .

[raveit65]

I will take a look at it, tomorrow. It's late in good old europe.

[lukefromdc]

Thanks

[lukefromdc]

I will now look at a decent default SSD decoration theme matching Menta for mate-wayland-session

[lukefromdc]

Moving general wayland discussions to https://github.com/orgs/mate-desktop/discussions/4

[lukefromdc]

Report from @zhuyaliang of memory leaks found. I still have the branch. Should I open a new PR to work on that, or rename my local branch, revert this, push the renamed branch and work on it there, or wait for a PR from @zhuyaliang?

OK with however we want to approach this

[lukefromdc]

Some help on where they are would help, though @zhuyaliang has said they might be able to cork them up later

[lukefromdc]

Also note that at least under wayland, the worst memory leak in caja seems to be on closing navigation and spatial windows(including but not limited to the desktop), and on closing caja itself Valgrind shows issues there, and at least in my run of it didn't detect whatever leaks are in my background handling code.

If I do a bunch of background changes, I don't see ram using going up, if I open and close a bunch of windows I don't need valgrind to find it as conky will easily show ram use growing. I sometimes see the same errors that show up if I close windows while running caja from a terminal in a plain wayfire session when running caja as root under x11 (or from the terminal in IceWM in x11) so I think those affect x11 too but for some reason not as badly.

Fixing memory leaks on closing windows or shutting down caja of course is a matter for a new PR.

[lukefromdc]

What might work best is this: on the backgrond changes, I wait for a PR from @zhuyaliang as I have been over it back and forth looking for leaks and Valgrind didn't show me any either (though part of its output was cut off in terminal).

Since the big leaks are probably easier to find, I will get to work on those window closing problems, where we get g_list_foreach (windows, (GFunc) gtk_widget_destroy, NULL); and a big memory leak. Looks like something is getting freed to soon and leaving its components in ram.

[lukefromdc]

Just managed to get ALL of the valgrind output for opening caja under wayland to only the desktop, changing the background once, then terminating caja with caja --quit. This includes setting up and taking down the desktop window as well as changing the background.

==216229== Memcheck, a memory error detector
==216229== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==216229== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
==216229== Command: caja -n --force-desktop
==216229== 
Initializing caja-sendto extension
Initializing caja-xattr-tags extension
Initializing caja-share extension
Initializing caja-open-terminal extension
Initializing caja-image-converter extension
Initializing caja-wallpaper extension
==216229== Invalid read of size 8
==216229==    at 0x57D920D: g_type_check_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CECF3: g_signal_handlers_disconnect_matched (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x18CA88: caja_window_finalize_menus (caja-window-menus.c:1059)
==216229==    by 0x18F7C8: caja_window_finalize (caja-window.c:712)
==216229==    by 0x57BAF0B: g_object_unref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0xE174B7C: ??? (in /usr/lib/python3/dist-packages/gi/_gi.cpython-311-x86_64-linux-gnu.so)
==216229==    by 0xE9E2E09: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xE9B82EC: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xE9BD96B: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xE174BD4: ??? (in /usr/lib/python3/dist-packages/gi/_gi.cpython-311-x86_64-linux-gnu.so)
==216229==    by 0xE9E2E09: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0x57BAF0B: g_object_unref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==  Address 0x101025b0 is 48 bytes inside a block of size 88 free'd
==216229==    at 0x48431EF: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x57D7733: g_type_free_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x236937: eel_debug_shut_down (eel-debug.c:87)
==216229==    by 0x15A200: main (caja-main.c:274)
==216229==  Block was alloc'd at
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57D72EE: g_type_create_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BB8AF: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BCD32: g_object_new_with_properties (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BDB30: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x220884: caja_trash_monitor_get (caja-trash-monitor.c:216)
==216229==    by 0x2208D8: caja_trash_monitor_get_icon (caja-trash-monitor.c:238)
==216229==    by 0x1D46DB: caja_desktop_link_new (caja-desktop-link.c:251)
==216229==    by 0x1D34E7: create_link_and_add_preference (caja-desktop-link-monitor.c:348)
==216229==    by 0x1D3716: caja_desktop_link_monitor_init (caja-desktop-link-monitor.c:390)
==216229==    by 0x57D723A: g_type_create_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
sys:1: Warning: instance with invalid (NULL) class pointer
sys:1: Warning: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
==216229== 
==216229== HEAP SUMMARY:
==216229==     in use at exit: 9,558,737 bytes in 54,461 blocks
==216229==   total heap usage: 963,057 allocs, 908,596 frees, 621,303,982 bytes allocated
==216229== 
==216229== 8 bytes in 1 blocks are possibly lost in loss record 863 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x1471BF8C: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E84E2: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E9375: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E6EE5: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145917C6: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145A18FF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141B1418: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145878EF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142B2B14: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x14207880: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 8 bytes in 1 blocks are possibly lost in loss record 864 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x1471BF8C: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E84E2: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E6EE5: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145918E8: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145A18FF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141B1418: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145878EF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142B2B14: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x14207880: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142079F8: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 10 bytes in 1 blocks are definitely lost in loss record 972 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x58776EE: g_strdup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x56B4D47: g_settings_get_string (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x198880: wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:272)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C81D6: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4E4072F: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 13 bytes in 1 blocks are definitely lost in loss record 1,154 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x58776EE: g_strdup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x56B4D47: g_settings_get_string (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x1988A9: wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:278)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C81D6: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4E4072F: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 15 bytes in 2 blocks are possibly lost in loss record 1,240 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x1471BF8C: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E84E2: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E843E: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145EAA59: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8D0F: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E6EE5: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x14591A2B: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145A18FF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141B1418: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145878EF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142B2B14: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 16 bytes in 1 blocks are definitely lost in loss record 3,917 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x4CC94AF: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4CC9562: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C8304: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4CCDB1E: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4CCC8E5: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4B5BCA3: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 16 bytes in 1 blocks are definitely lost in loss record 3,918 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x58776EE: g_strdup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x56B4D47: g_settings_get_string (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x198892: wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:275)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C81D6: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4E4072F: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 18 bytes in 1 blocks are definitely lost in loss record 4,030 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x58776EE: g_strdup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x56B4D47: g_settings_get_string (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x1988BD: wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:281)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C81D6: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4E4072F: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 19 bytes in 2 blocks are definitely lost in loss record 4,090 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x58776EE: g_strdup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x569C8E0: g_application_run (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x15A1F1: main (caja-main.c:269)
==216229== 
==216229== 21 bytes in 3 blocks are possibly lost in loss record 4,202 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x1471BF8C: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E84E2: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145EAA59: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E9375: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E6EE5: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145917C6: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145A18FF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141B1418: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145878EF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 21 bytes in 3 blocks are possibly lost in loss record 4,203 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x1471BF8C: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E84E2: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145EAA59: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E6EE5: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145918E8: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145A18FF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141B1418: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145878EF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142B2B14: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 32 bytes in 1 blocks are possibly lost in loss record 8,899 of 19,249
==216229==    at 0x4840718: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D6DD: g_realloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF92B: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FB14: caja_icon_info_get_pixbuf_nodefault_at_size (caja-icon-info.c:545)
==216229==    by 0x20FBED: caja_icon_info_get_surface_nodefault_at_size (caja-icon-info.c:573)
==216229==    by 0x22225A: get_action_icon (caja-ui-utilities.c:167)
==216229==    by 0x222516: caja_action_from_menu_item (caja-ui-utilities.c:199)
==216229==    by 0x18BFA8: add_extension_menu_items (caja-window-menus.c:1124)
==216229==    by 0x18CBF4: caja_window_load_extension_menus (caja-window-menus.c:1209)
==216229==    by 0x18A9B9: update_for_new_location (caja-window-manage-views.c:1857)
==216229==    by 0x18A9B9: location_has_really_changed (caja-window-manage-views.c:1642)
==216229==    by 0x18A9B9: caja_window_report_load_underway (caja-window-manage-views.c:1560)
==216229==    by 0x19FC57: finish_loading (fm-directory-view.c:9715)
==216229== 
==216229== 32 bytes in 1 blocks are possibly lost in loss record 8,900 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5835F29: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF8DE: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FB14: caja_icon_info_get_pixbuf_nodefault_at_size (caja-icon-info.c:545)
==216229==    by 0x20FBED: caja_icon_info_get_surface_nodefault_at_size (caja-icon-info.c:573)
==216229==    by 0x22225A: get_action_icon (caja-ui-utilities.c:167)
==216229==    by 0x222516: caja_action_from_menu_item (caja-ui-utilities.c:199)
==216229==    by 0x18BFA8: add_extension_menu_items (caja-window-menus.c:1124)
==216229==    by 0x18CBF4: caja_window_load_extension_menus (caja-window-menus.c:1209)
==216229==    by 0x18A9B9: update_for_new_location (caja-window-manage-views.c:1857)
==216229==    by 0x18A9B9: location_has_really_changed (caja-window-manage-views.c:1642)
==216229==    by 0x18A9B9: caja_window_report_load_underway (caja-window-manage-views.c:1560)
==216229== 
==216229== 32 bytes in 1 blocks are possibly lost in loss record 8,901 of 19,249
==216229==    at 0x4840718: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D6DD: g_realloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF92B: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FB14: caja_icon_info_get_pixbuf_nodefault_at_size (caja-icon-info.c:545)
==216229==    by 0x20FBED: caja_icon_info_get_surface_nodefault_at_size (caja-icon-info.c:573)
==216229==    by 0x199E67: get_menu_icon (fm-directory-view.c:4948)
==216229==    by 0x19BAFB: connect_proxy (fm-directory-view.c:7694)
==216229==    by 0x19BAFB: connect_proxy (fm-directory-view.c:7679)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C81D6: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 32 bytes in 1 blocks are possibly lost in loss record 8,902 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5835F29: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF8DE: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FB14: caja_icon_info_get_pixbuf_nodefault_at_size (caja-icon-info.c:545)
==216229==    by 0x20FBED: caja_icon_info_get_surface_nodefault_at_size (caja-icon-info.c:573)
==216229==    by 0x199E67: get_menu_icon (fm-directory-view.c:4948)
==216229==    by 0x19BAFB: connect_proxy (fm-directory-view.c:7694)
==216229==    by 0x19BAFB: connect_proxy (fm-directory-view.c:7679)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C81D6: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 32 bytes in 1 blocks are possibly lost in loss record 8,903 of 19,249
==216229==    at 0x4840718: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D6DD: g_realloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF92B: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FA68: caja_icon_info_get_pixbuf (caja-icon-info.c:507)
==216229==    by 0x201267: caja_icon_container_update_icon (caja-icon-container.c:7643)
==216229==    by 0x2019B9: caja_icon_container_request_update (caja-icon-container.c:8000)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C883C: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 32 bytes in 1 blocks are possibly lost in loss record 8,904 of 19,249
==216229==    at 0x4840718: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D6DD: g_realloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF92B: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x1F6E33: caja_file_get_emblem_pixbufs (caja-file.c:6997)
==216229==    by 0x1AC30C: fm_icon_container_get_icon_images (fm-icon-container.c:93)
==216229==    by 0x201085: caja_icon_container_get_icon_images (caja-icon-container.c:7430)
==216229==    by 0x201085: caja_icon_container_update_icon (caja-icon-container.c:7633)
==216229==    by 0x207897: finish_adding_new_icons (caja-icon-container.c:7743)
==216229==    by 0x207897: redo_layout_internal (caja-icon-container.c:2354)
==216229==    by 0x20BAD8: redo_layout_callback (caja-icon-container.c:2386)
==216229==    by 0x5853BA8: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5856B46: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x585712B: g_main_context_iteration (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229== 
==216229== 32 bytes in 1 blocks are possibly lost in loss record 8,905 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5835F29: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF8DE: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x1F6E33: caja_file_get_emblem_pixbufs (caja-file.c:6997)
==216229==    by 0x1AC30C: fm_icon_container_get_icon_images (fm-icon-container.c:93)
==216229==    by 0x201085: caja_icon_container_get_icon_images (caja-icon-container.c:7430)
==216229==    by 0x201085: caja_icon_container_update_icon (caja-icon-container.c:7633)
==216229==    by 0x207897: finish_adding_new_icons (caja-icon-container.c:7743)
==216229==    by 0x207897: redo_layout_internal (caja-icon-container.c:2354)
==216229==    by 0x20BAD8: redo_layout_callback (caja-icon-container.c:2386)
==216229==    by 0x5853BA8: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5856B46: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229== 
==216229== 35 bytes in 1 blocks are definitely lost in loss record 9,048 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x58776EE: g_strdup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x56B4D47: g_settings_get_string (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x19886C: wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:269)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C81D6: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4E4072F: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 36 bytes in 1 blocks are possibly lost in loss record 9,067 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x53D9D7D: pango_language_from_string (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53D9E78: pango_language_get_default (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53D50C7: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x57D723A: g_type_create_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BB8AF: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BCD32: g_object_new_with_properties (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BDB30: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x53D7106: pango_font_map_create_context (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x52D89AB: gdk_pango_context_get_for_screen (in /usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2408.32)
==216229==    by 0x4E078CE: gtk_widget_create_pango_context (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 40 bytes in 1 blocks are definitely lost in loss record 10,063 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x58776EE: g_strdup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x4C3F696: gtk_file_chooser_get_filename (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x1985F5: update_background_image (fm-desktop-wayland-bg-dialog.c:244)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9BEB: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57B826B: g_cclosure_marshal_VOID__BOOLEANv (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9BEB: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 43 (32 direct, 11 indirect) bytes in 1 blocks are definitely lost in loss record 10,090 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57D71AA: g_type_create_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BB8AF: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BCD32: g_object_new_with_properties (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BDB30: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x56EFA8A: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x4CF4AF3: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4C54F82: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4C5729D: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x566EF32: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x566EF68: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229== 
==216229== 48 bytes in 1 blocks are possibly lost in loss record 11,215 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC9C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5820476: g_atomic_rc_box_dup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x1F1979: caja_file_new_from_filename (caja-file.c:538)
==216229==    by 0x1F1979: caja_file_get_internal (caja-file.c:702)
==216229==    by 0x1F22EA: caja_file_get_by_uri (caja-file.c:749)
==216229==    by 0x1EF1D7: update_xdg_dir_cache (caja-file-utilities.c:444)
==216229==    by 0x1EF864: caja_get_xdg_dir (caja-file-utilities.c:479)
==216229==    by 0x1EF945: caja_get_desktop_directory (caja-file-utilities.c:526)
==216229==    by 0x15BD2D: check_required_directories (caja-application.c:522)
==216229==    by 0x15BD2D: caja_application_startup (caja-application.c:2328)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9BEB: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 48 bytes in 1 blocks are possibly lost in loss record 11,216 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC9C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5820476: g_atomic_rc_box_dup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x1F188D: caja_file_new_from_filename (caja-file.c:538)
==216229==    by 0x1F188D: caja_file_get_internal (caja-file.c:702)
==216229==    by 0x188795: begin_location_change (caja-window-manage-views.c:1006)
==216229==    by 0x188C09: caja_window_slot_open_location_full (caja-window-manage-views.c:699)
==216229==    by 0x1902E8: caja_window_go_to (caja-window.c:238)
==216229==    by 0x164688: caja_desktop_window_update_directory (caja-desktop-window.c:150)
==216229==    by 0x1648E9: caja_desktop_window_new (caja-desktop-window.c:284)
==216229==    by 0x15B861: caja_application_create_desktop_windows (caja-application.c:719)
==216229==    by 0x15BE15: caja_application_open_desktop (caja-application.c:745)
==216229==    by 0x15BE15: init_desktop (caja-application.c:2193)
==216229==    by 0x15BE15: caja_application_startup (caja-application.c:2329)
==216229== 
==216229== 48 bytes in 1 blocks are possibly lost in loss record 11,217 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC9C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5820476: g_atomic_rc_box_dup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586B65F: g_ref_string_new_intern (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x1FA3A1: update_info_internal (caja-file.c:2359)
==216229==    by 0x1D9FD5: query_info_callback (caja-directory-async.c:3703)
==216229==    by 0x566EF32: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x566EF68: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x5853BA8: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5856B46: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x585712B: g_main_context_iteration (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229== 
==216229== 48 bytes in 1 blocks are possibly lost in loss record 11,218 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC9C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5820476: g_atomic_rc_box_dup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586B65F: g_ref_string_new_intern (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x1FA6BE: update_info_internal (caja-file.c:2466)
==216229==    by 0x1D9FD5: query_info_callback (caja-directory-async.c:3703)
==216229==    by 0x566EF32: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x566EF68: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x5853BA8: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5856B46: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x585712B: g_main_context_iteration (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229== 
==216229== 48 bytes in 1 blocks are possibly lost in loss record 11,219 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC9C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5820476: g_atomic_rc_box_dup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586B65F: g_ref_string_new_intern (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x1FA77D: update_info_internal (caja-file.c:2487)
==216229==    by 0x1D9FD5: query_info_callback (caja-directory-async.c:3703)
==216229==    by 0x566EF32: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x566EF68: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x5853BA8: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5856B46: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x585712B: g_main_context_iteration (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229== 
==216229== 48 bytes in 1 blocks are possibly lost in loss record 11,220 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D6DD: g_realloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF8AC: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FA68: caja_icon_info_get_pixbuf (caja-icon-info.c:507)
==216229==    by 0x201267: caja_icon_container_update_icon (caja-icon-container.c:7643)
==216229==    by 0x2019B9: caja_icon_container_request_update (caja-icon-container.c:8000)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C883C: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 48 (32 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record 11,227 of 19,249
==216229==    at 0x57D7351: g_type_create_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BB8AF: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BCD32: g_object_new_with_properties (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BDB30: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x22BA5F: egg_sm_client_get (eggsmclient.c:372)
==216229==    by 0x22BB31: sm_client_post_parse_func (eggsmclient.c:195)
==216229==    by 0x5865B58: g_option_context_parse (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x15C9B5: caja_application_local_command_line (caja-application.c:1985)
==216229==    by 0x569C935: g_application_run (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x15A1F1: main (caja-main.c:269)
==216229== 
==216229== 50 bytes in 2 blocks are definitely lost in loss record 11,236 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x5E83017: __vasprintf_internal (vasprintf.c:116)
==216229==    by 0x58A9082: g_vasprintf (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x587789F: g_strdup_vprintf (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x587793B: g_strdup_printf (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0xDDF0437: caja_python_object_get_type (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0xDDEECB1: ??? (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0xDDEF1C9: caja_module_initialize (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0x2157A1: caja_module_load (caja-module.c:104)
==216229==    by 0x57DACE8: g_type_module_use (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x2159C0: caja_module_load_file (caja-module.c:202)
==216229==    by 0x2159C0: load_module_dir (caja-module.c:235)
==216229==    by 0x215B95: caja_module_setup (caja-module.c:278)
==216229== 
==216229== 64 bytes in 2 blocks are possibly lost in loss record 12,411 of 19,249
==216229==    at 0x4840718: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D6DD: g_realloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF92B: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FA68: caja_icon_info_get_pixbuf (caja-icon-info.c:507)
==216229==    by 0x20FC44: caja_icon_info_get_pixbuf_at_size (caja-icon-info.c:591)
==216229==    by 0x20FD1D: caja_icon_info_get_surface_at_size (caja-icon-info.c:619)
==216229==    by 0x1CD2FE: caja_bookmark_get_surface (caja-bookmark.c:234)
==216229==    by 0x18C5DE: caja_menus_append_bookmark_to_menu (caja-window-menus.c:192)
==216229==    by 0x187C72: update_bookmarks (caja-window-bookmarks.c:255)
==216229==    by 0x187C72: refresh_bookmarks_menu (caja-window-bookmarks.c:274)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C81D6: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 64 bytes in 2 blocks are possibly lost in loss record 12,412 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5835F29: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF8DE: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FA68: caja_icon_info_get_pixbuf (caja-icon-info.c:507)
==216229==    by 0x20FC44: caja_icon_info_get_pixbuf_at_size (caja-icon-info.c:591)
==216229==    by 0x20FD1D: caja_icon_info_get_surface_at_size (caja-icon-info.c:619)
==216229==    by 0x1CD2FE: caja_bookmark_get_surface (caja-bookmark.c:234)
==216229==    by 0x18C5DE: caja_menus_append_bookmark_to_menu (caja-window-menus.c:192)
==216229==    by 0x187C72: update_bookmarks (caja-window-bookmarks.c:255)
==216229==    by 0x187C72: refresh_bookmarks_menu (caja-window-bookmarks.c:274)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 64 bytes in 2 blocks are possibly lost in loss record 12,413 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5835F29: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF8DE: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FA68: caja_icon_info_get_pixbuf (caja-icon-info.c:507)
==216229==    by 0x201267: caja_icon_container_update_icon (caja-icon-container.c:7643)
==216229==    by 0x2019B9: caja_icon_container_request_update (caja-icon-container.c:8000)
==216229==    by 0x57B6197: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C883C: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9AD0: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 96 bytes in 1 blocks are possibly lost in loss record 16,213 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC41: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x63C1AA9: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53D5BC4: pango_context_get_metrics (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x4BA0BA3: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BEB034: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4B97F08: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BEB034: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4D13FE7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BE5E12: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BEB034: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 96 bytes in 1 blocks are possibly lost in loss record 16,214 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC41: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x63C1AA9: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53A1581: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x53D5203: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x63C0E28: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53D5BE6: pango_context_get_metrics (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x4BA0BA3: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 96 bytes in 1 blocks are possibly lost in loss record 16,215 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC41: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x63C1AA9: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2279: pango_layout_get_size (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x143DB101: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142BD533: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x14307DCD: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142BF9D7: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 96 bytes in 1 blocks are possibly lost in loss record 16,216 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC41: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x63C1AA9: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2A67: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53EB356: pango_renderer_draw_layout (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53A4E07: pango_cairo_layout_path (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x143168E2: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142C1400: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x14311101: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 104 bytes in 2 blocks are possibly lost in loss record 16,450 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x4BFC915: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BFCCD7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BFB63C: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E65736: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E67092: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E672AD: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57BB982: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BD7D2: g_object_new_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BDB1B: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4E65CA7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 112 bytes in 2 blocks are possibly lost in loss record 16,699 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x4BFC915: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BFCCD7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BFB63C: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E65736: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E67064: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E672AD: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57BB982: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BD7D2: g_object_new_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BDB1B: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4E65CA7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 116 bytes in 1 blocks are possibly lost in loss record 16,701 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x141B2FDC: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145F5138: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145AE043: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145C2FB5: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145C18BC: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145A5043: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145876CB: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142B2B14: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x14207880: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142079F8: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x14207504: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 128 bytes in 1 blocks are definitely lost in loss record 17,020 of 19,249
==216229==    at 0x4840718: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D6DD: g_realloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x587A131: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x587A19B: g_string_sized_new (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x583FB6D: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5841037: g_build_filename (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0xDDEF1E8: caja_module_initialize (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0x2157A1: caja_module_load (caja-module.c:104)
==216229==    by 0x57DACE8: g_type_module_use (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x2159C0: caja_module_load_file (caja-module.c:202)
==216229==    by 0x2159C0: load_module_dir (caja-module.c:235)
==216229==    by 0x215B95: caja_module_setup (caja-module.c:278)
==216229==    by 0x15BBC5: caja_application_startup (caja-application.c:2295)
==216229== 
==216229== 144 bytes in 2 blocks are definitely lost in loss record 17,203 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0xDDF03E0: caja_python_object_get_type (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0xDDEECB1: ??? (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0xDDEF1C9: caja_module_initialize (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0x2157A1: caja_module_load (caja-module.c:104)
==216229==    by 0x57DACE8: g_type_module_use (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x2159C0: caja_module_load_file (caja-module.c:202)
==216229==    by 0x2159C0: load_module_dir (caja-module.c:235)
==216229==    by 0x215B95: caja_module_setup (caja-module.c:278)
==216229==    by 0x15BBC5: caja_application_startup (caja-application.c:2295)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9BEB: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 144 (112 direct, 32 indirect) bytes in 2 blocks are definitely lost in loss record 17,204 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D6DD: g_realloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5835FE4: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57B9D60: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BAE33: g_object_unref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x2155AE: free_module_objects (caja-module.c:251)
==216229==    by 0x236937: eel_debug_shut_down (eel-debug.c:87)
==216229==    by 0x15A200: main (caja-main.c:274)
==216229== 
==216229== 144 (96 direct, 48 indirect) bytes in 3 blocks are definitely lost in loss record 17,205 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5835F29: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57B9D60: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BAE33: g_object_unref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57DBA67: g_value_unset (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C948C: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x48DD309: ??? (in /usr/lib/x86_64-linux-gnu/libmate-desktop-2.so.17.1.4)
==216229==    by 0x5853168: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5853A0E: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229== 
==216229== 148 bytes in 1 blocks are possibly lost in loss record 17,209 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x141B28C4: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145F53D8: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145AE216: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E856D: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E843E: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145EAA59: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8D0F: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E6EE5: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x14591A2B: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145A18FF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141B1418: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 160 bytes in 10 blocks are possibly lost in loss record 17,294 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63E6E61: FcFontSetCreate (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63ED48D: FcFontSetSort (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63BF350: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x588227C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5E8E3EB: start_thread (pthread_create.c:444)
==216229==    by 0x5F0E97F: clone (clone.S:100)
==216229== 
==216229== 161 (64 direct, 97 indirect) bytes in 1 blocks are definitely lost in loss record 17,302 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x589ECDD: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x589B620: g_variant_builder_end (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x56CBA16: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x56CB9DB: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x56CE140: g_dbus_message_new_from_blob (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x56D8407: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x566EF32: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x566EF68: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x5853BA8: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5856B46: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229== 
==216229== 168 bytes in 7 blocks are possibly lost in loss record 17,375 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EF146: FcPatternCreate (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63EC478: FcFontRenderPrepare (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63ECD4D: FcFontSetMatch (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63BF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x588227C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5E8E3EB: start_thread (pthread_create.c:444)
==216229==    by 0x5F0E97F: clone (clone.S:100)
==216229== 
==216229== 192 bytes in 2 blocks are possibly lost in loss record 17,545 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC41: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x63C1AA9: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x4CA38F0: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BE5E12: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BEB034: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4C9EFA2: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4D51368: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 240 bytes in 5 blocks are possibly lost in loss record 17,724 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x587772B: g_memdup (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x4BFCC28: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BFB5FC: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4D5F8F0: gtk_style_context_set_state (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E6702B: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E672AD: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57BB982: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BD7D2: g_object_new_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BDB1B: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4E65CA7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 260 bytes in 5 blocks are possibly lost in loss record 17,848 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x4BFC915: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BFCCD7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BFB63C: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E67051: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E672AD: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x57BB982: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BD7D2: g_object_new_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BDB1B: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x4E65CA7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4E65CED: gtk_style_new (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 280 bytes in 1 blocks are possibly lost in loss record 17,910 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x141B28C4: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145F53D8: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145AE216: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E856D: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145EAA59: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E9375: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E6EE5: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145917C6: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145A18FF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 280 bytes in 1 blocks are possibly lost in loss record 17,911 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x141B28C4: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145F53D8: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145AE216: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E856D: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145EAA59: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E8EC0: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145E6EE5: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145918E8: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x145A18FF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141B1418: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 384 bytes in 4 blocks are possibly lost in loss record 18,128 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x586AC41: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x63C1AA9: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53A1581: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x53DBBEF: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DBE88: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DCC68: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E1F28: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229== 
==216229== 416 bytes in 1 blocks are possibly lost in loss record 18,188 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x4011082: calloc (rtld-malloc.h:44)
==216229==    by 0x4011082: allocate_dtv (dl-tls.c:375)
==216229==    by 0x4011A7D: _dl_allocate_tls (dl-tls.c:634)
==216229==    by 0x5E8EFBE: allocate_stack (allocatestack.c:423)
==216229==    by 0x5E8EFBE: pthread_create@@GLIBC_2.34 (pthread_create.c:652)
==216229==    by 0x58ADD85: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5882599: g_thread_new (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5882FB6: g_thread_pool_new_full (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x566ED3A: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x566F0AC: g_task_get_type (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x56D6EAC: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x56D5942: g_dbus_proxy_new_for_bus (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x5307CF0: ??? (in /usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2408.32)
==216229== 
==216229== 416 bytes in 1 blocks are possibly lost in loss record 18,189 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x4011082: calloc (rtld-malloc.h:44)
==216229==    by 0x4011082: allocate_dtv (dl-tls.c:375)
==216229==    by 0x4011A7D: _dl_allocate_tls (dl-tls.c:634)
==216229==    by 0x5E8EFBE: allocate_stack (allocatestack.c:423)
==216229==    by 0x5E8EFBE: pthread_create@@GLIBC_2.34 (pthread_create.c:652)
==216229==    by 0x58ADD85: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5882599: g_thread_new (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5858003: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x566EDB6: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x566F0AC: g_task_get_type (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x56D6EAC: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x56D5942: g_dbus_proxy_new_for_bus (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x5307CF0: ??? (in /usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2408.32)
==216229== 
==216229== 416 bytes in 1 blocks are possibly lost in loss record 18,190 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x4011082: calloc (rtld-malloc.h:44)
==216229==    by 0x4011082: allocate_dtv (dl-tls.c:375)
==216229==    by 0x4011A7D: _dl_allocate_tls (dl-tls.c:634)
==216229==    by 0x5E8EFBE: allocate_stack (allocatestack.c:423)
==216229==    by 0x5E8EFBE: pthread_create@@GLIBC_2.34 (pthread_create.c:652)
==216229==    by 0x58ADD85: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5882599: g_thread_new (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x4866989: ??? (in /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so)
==216229==    by 0x4866D5E: ??? (in /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so)
==216229==    by 0x4862EEE: ??? (in /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so)
==216229==    by 0x57BB982: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BD7D2: g_object_new_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57BDB1B: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 416 bytes in 1 blocks are possibly lost in loss record 18,191 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x4011082: calloc (rtld-malloc.h:44)
==216229==    by 0x4011082: allocate_dtv (dl-tls.c:375)
==216229==    by 0x4011A7D: _dl_allocate_tls (dl-tls.c:634)
==216229==    by 0x5E8EFBE: allocate_stack (allocatestack.c:423)
==216229==    by 0x5E8EFBE: pthread_create@@GLIBC_2.34 (pthread_create.c:652)
==216229==    by 0x58ADD85: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5882599: g_thread_new (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x56D8D7E: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x56CA40D: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x56CABFE: g_bus_get_sync (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229==    by 0x4866AD3: ??? (in /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so)
==216229==    by 0x4866BDE: ??? (in /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so)
==216229==    by 0x5853BA8: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229== 
==216229== 448 bytes in 14 blocks are possibly lost in loss record 18,227 of 19,249
==216229==    at 0x4840718: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D6DD: g_realloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF92B: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FA68: caja_icon_info_get_pixbuf (caja-icon-info.c:507)
==216229==    by 0x201267: caja_icon_container_update_icon (caja-icon-container.c:7643)
==216229==    by 0x207897: finish_adding_new_icons (caja-icon-container.c:7743)
==216229==    by 0x207897: redo_layout_internal (caja-icon-container.c:2354)
==216229==    by 0x20BAD8: redo_layout_callback (caja-icon-container.c:2386)
==216229==    by 0x5853BA8: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5856B46: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x585712B: g_main_context_iteration (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x569C99C: g_application_run (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229== 
==216229== 448 bytes in 14 blocks are possibly lost in loss record 18,228 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5835F29: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x57BF8DE: g_object_add_toggle_ref (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x20F9FD: caja_icon_info_get_pixbuf_nodefault (caja-icon-info.c:480)
==216229==    by 0x20FA68: caja_icon_info_get_pixbuf (caja-icon-info.c:507)
==216229==    by 0x201267: caja_icon_container_update_icon (caja-icon-container.c:7643)
==216229==    by 0x207897: finish_adding_new_icons (caja-icon-container.c:7743)
==216229==    by 0x207897: redo_layout_internal (caja-icon-container.c:2354)
==216229==    by 0x20BAD8: redo_layout_callback (caja-icon-container.c:2386)
==216229==    by 0x5853BA8: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5856B46: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x585712B: g_main_context_iteration (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229== 
==216229== 480 (288 direct, 192 indirect) bytes in 4 blocks are definitely lost in loss record 18,251 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D695: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x584D98A: g_key_file_new (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x1E1785: extension_new (caja-extensions.c:55)
==216229==    by 0x1E1785: caja_extension_register (caja-extensions.c:218)
==216229==    by 0x215A6E: add_module_objects (caja-module.c:189)
==216229==    by 0x215A6E: caja_module_load_file (caja-module.c:204)
==216229==    by 0x215A6E: load_module_dir (caja-module.c:235)
==216229==    by 0x215B95: caja_module_setup (caja-module.c:278)
==216229==    by 0x15BBC5: caja_application_startup (caja-application.c:2295)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57C9BEB: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF401: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x57CF4A1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x569C2B1: g_application_register (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7800.3)
==216229== 
==216229== 512 bytes in 1 blocks are possibly lost in loss record 18,306 of 19,249
==216229==    at 0x48459F3: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x4011082: calloc (rtld-malloc.h:44)
==216229==    by 0x4011082: allocate_dtv (dl-tls.c:375)
==216229==    by 0x4011A7D: _dl_allocate_tls (dl-tls.c:634)
==216229==    by 0x5E8EFBE: allocate_stack (allocatestack.c:423)
==216229==    by 0x5E8EFBE: pthread_create@@GLIBC_2.34 (pthread_create.c:652)
==216229==    by 0x58ADD85: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5882895: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x588227C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5E8E3EB: start_thread (pthread_create.c:444)
==216229==    by 0x5F0E97F: clone (clone.S:100)
==216229== 
==216229== 528 bytes in 1 blocks are possibly lost in loss record 18,326 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0xE9D4247: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAD86F8: _PyObject_GC_NewVar (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xE9A7907: PyList_AsTuple (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA7EBA: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEBCB187: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAAED90: Py_InitializeFromConfig (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAAEF9B: Py_InitializeEx (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xDDEE7A3: ??? (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0xDDEF1C9: caja_module_initialize (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0x2157A1: caja_module_load (caja-module.c:104)
==216229==    by 0x57DACE8: g_type_module_use (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== 600 bytes in 1 blocks are possibly lost in loss record 18,381 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0xE9D4247: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAD86F8: _PyObject_GC_NewVar (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xE9DD347: PyTuple_New (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1C7A: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1F13: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1CA2: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1F13: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA39B7: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA3AE7: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xE9114C9: _PyEval_EvalFrameDefault (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEA69AC1: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229== 
==216229== 608 bytes in 1 blocks are possibly lost in loss record 18,395 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0xE9D4247: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAD86F8: _PyObject_GC_NewVar (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xE9DD347: PyTuple_New (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1C7A: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1F2C: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1CA2: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1F13: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA39B7: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA3AE7: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xE9114C9: _PyEval_EvalFrameDefault (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEA69AC1: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229== 
==216229== 1,056 bytes in 2 blocks are possibly lost in loss record 18,688 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0xE9D4247: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAD86F8: _PyObject_GC_NewVar (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xE9DD347: PyTuple_New (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1C7A: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1F2C: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1CA2: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1F13: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1CA2: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA1F13: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA39B7: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229==    by 0xEAA3AE7: ??? (in /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0)
==216229== 
==216229== 2,128 bytes in 1 blocks are possibly lost in loss record 18,919 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x141A7D24: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141EB9FF: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142C7164: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141BFB6C: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142B0AED: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x1467D720: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141AA4A1: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x141E71E9: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x1429AE70: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x1421EE24: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x1421D0DD: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 2,507 (768 direct, 1,739 indirect) bytes in 1 blocks are definitely lost in loss record 18,951 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63F0209: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63EC784: FcFontRenderPrepare (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63C09D3: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x63C0E39: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53D5BE6: pango_context_get_metrics (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x4BA0BA3: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BEB034: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4B97F08: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BEB034: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4D13FE7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 2,517 (768 direct, 1,749 indirect) bytes in 1 blocks are definitely lost in loss record 18,952 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63F0209: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63EC784: FcFontRenderPrepare (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63C09D3: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x63C0E39: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CED73: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53CF75E: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x4CA38F0: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BE5E12: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 2,539 (768 direct, 1,771 indirect) bytes in 1 blocks are definitely lost in loss record 18,953 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63F0209: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63EC784: FcFontRenderPrepare (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63C09D3: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x63C0E39: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CED73: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53CF75E: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2279: pango_layout_get_size (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x143DB101: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 2,539 (768 direct, 1,771 indirect) bytes in 1 blocks are definitely lost in loss record 18,954 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63F0209: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63EC784: FcFontRenderPrepare (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63C09D3: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x63C0E39: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CED73: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53CF75E: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2A67: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53EB356: pango_renderer_draw_layout (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53A4E07: pango_cairo_layout_path (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229== 
==216229== 2,560 bytes in 10 blocks are possibly lost in loss record 18,957 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63E6F47: FcFontSetAdd (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63ED549: FcFontSetSort (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63BF350: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x588227C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5E8E3EB: start_thread (pthread_create.c:444)
==216229==    by 0x5F0E97F: clone (clone.S:100)
==216229== 
==216229== 3,366 (2,560 direct, 806 indirect) bytes in 10 blocks are definitely lost in loss record 19,011 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFAE1: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63F0318: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63F1C8D: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63FA75C: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x6A20681: ??? (in /usr/lib/x86_64-linux-gnu/libexpat.so.1.8.10)
==216229==    by 0x6A21983: ??? (in /usr/lib/x86_64-linux-gnu/libexpat.so.1.8.10)
==216229==    by 0x6A23D9C: ??? (in /usr/lib/x86_64-linux-gnu/libexpat.so.1.8.10)
==216229==    by 0x6A1B959: XML_ParseBuffer (in /usr/lib/x86_64-linux-gnu/libexpat.so.1.8.10)
==216229==    by 0x63F785C: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63F8008: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63F8078: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229== 
==216229== 6,273 (512 direct, 5,761 indirect) bytes in 1 blocks are definitely lost in loss record 19,099 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63D9E4F: FcConfigSubstituteWithPat (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x53A5862: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x63C19ED: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53D5BC4: pango_context_get_metrics (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x4BA0BA3: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BEB034: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4B97F08: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BEB034: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4D13FE7: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BE5E12: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 6,318 (512 direct, 5,806 indirect) bytes in 1 blocks are definitely lost in loss record 19,100 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63D9E4F: FcConfigSubstituteWithPat (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x53A5862: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x63C19ED: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2279: pango_layout_get_size (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x143DB101: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142BD533: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x14307DCD: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 6,318 (512 direct, 5,806 indirect) bytes in 1 blocks are definitely lost in loss record 19,101 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63D9E4F: FcConfigSubstituteWithPat (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x53A5862: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x63C19ED: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2A67: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53EB356: pango_renderer_draw_layout (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53A4E07: pango_cairo_layout_path (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x143168E2: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229==    by 0x142C1400: ??? (in /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0)
==216229== 
==216229== 6,408 (512 direct, 5,896 indirect) bytes in 1 blocks are definitely lost in loss record 19,102 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63D9E4F: FcConfigSubstituteWithPat (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x53A5862: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x63C19ED: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53A1581: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x53D5203: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x63C0E28: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53D5BE6: pango_context_get_metrics (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229== 
==216229== 12,546 (1,024 direct, 11,522 indirect) bytes in 2 blocks are definitely lost in loss record 19,157 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63D9E4F: FcConfigSubstituteWithPat (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x53A5862: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x63C19ED: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x4CA38F0: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BE5E12: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4BEB034: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229==    by 0x4C9EFA2: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2408.32)
==216229== 
==216229== 16,384 bytes in 1 blocks are definitely lost in loss record 19,174 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5868A51: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x581DF14: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x4004E3D: call_init (dl-init.c:74)
==216229==    by 0x4004E3D: call_init (dl-init.c:26)
==216229==    by 0x4004F23: _dl_init (dl-init.c:121)
==216229==    by 0x401A4FF: ??? (in /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2)
==216229==    by 0x2: ???
==216229==    by 0x1FFF000B8A: ???
==216229==    by 0x1FFF000B8F: ???
==216229==    by 0x1FFF000B92: ???
==216229== 
==216229== 25,598 (7,680 direct, 17,918 indirect) bytes in 10 blocks are definitely lost in loss record 19,191 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63F0209: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63EC784: FcFontRenderPrepare (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63ECD4D: FcFontSetMatch (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63BF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x588227C: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x5E8E3EB: start_thread (pthread_create.c:444)
==216229==    by 0x5F0E97F: clone (clone.S:100)
==216229== 
==216229== 25,632 (2,048 direct, 23,584 indirect) bytes in 4 blocks are definitely lost in loss record 19,192 of 19,249
==216229==    at 0x4845C43: realloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x63EFB88: ??? (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x63D9E4F: FcConfigSubstituteWithPat (in /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0)
==216229==    by 0x53A5862: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x63C19ED: ??? (in /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0.5100.0)
==216229==    by 0x53CF3E6: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DF765: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53E2035: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53A1581: ??? (in /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0.5100.0)
==216229==    by 0x53DBBEF: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DBE88: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229==    by 0x53DCC68: ??? (in /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.5100.0)
==216229== 
==216229== 32,824 (8 direct, 32,816 indirect) bytes in 1 blocks are definitely lost in loss record 19,211 of 19,249
==216229==    at 0x4840808: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==216229==    by 0x585D64D: g_malloc (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x587776F: g_memdup2 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0x583E244: g_dir_open (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.3)
==216229==    by 0xDDEE6DC: ??? (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0xDDEF1C9: caja_module_initialize (in /usr/lib/x86_64-linux-gnu/caja/extensions-2.0/libcaja-python.so)
==216229==    by 0x2157A1: caja_module_load (caja-module.c:104)
==216229==    by 0x57DACE8: g_type_module_use (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229==    by 0x2159C0: caja_module_load_file (caja-module.c:202)
==216229==    by 0x2159C0: load_module_dir (caja-module.c:235)
==216229==    by 0x215B95: caja_module_setup (caja-module.c:278)
==216229==    by 0x15BBC5: caja_application_startup (caja-application.c:2295)
==216229==    by 0x57B6390: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7800.3)
==216229== 
==216229== LEAK SUMMARY:
==216229==    definitely lost: 35,937 bytes in 62 blocks
==216229==    indirectly lost: 117,341 bytes in 3,388 blocks
==216229==      possibly lost: 14,193 bytes in 124 blocks
==216229==    still reachable: 9,108,098 bytes in 48,298 blocks
==216229==         suppressed: 0 bytes in 0 blocks
==216229== Reachable blocks (those to which a pointer was found) are not shown.
==216229== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==216229== 
==216229== For lists of detected and suppressed errors, rerun with: -s
==216229== ERROR SUMMARY: 83 errors from 83 contexts (suppressed: 0 from 0)

[lukefromdc]

This is what I found when I searched every new function for wayland background handling against the valgrind output:

wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:269)  (35 bytes)
wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:272)  (10 bytes)
wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:275)  (16 bytes)
wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:278)  (13 bytes)
wayland_bg_dialog_new (fm-desktop-wayland-bg-dialog.c:281)  (18 bytes)

These leaked 92 bytes and all are related to variables declared in this block of code, probably the const is getting discarded without the compiler giving me a warning. That in turn is probably my default CFLAGS:

    const gchar *filename, *options;
    const gchar *shading_type, *primary_color_str, *secondary_color_str;

update_background_image (fm-desktop-wayland-bg-dialog.c:244) (40 bytes)

This leaks 40 bytes. and is related to line 244 which is const gchar *filename = gtk_file_chooser_get_filename (GTK_FILE_CHOOSER (filebutton));

eel_background_draw NOT FOUND by valgrind

action_change_background_callbackin fm-desktop-icon-view.c NOT FOUND by valgrind

Thus the wayland background code on a single change of image backgrounds is leaking 132 bytes amd all of these are problems with variables declared as const. I will try declaring them as gchar *filename (etc) and freeing them after

Meawhile we have things like pango leaking tens of KB in minutes

[zhuyaliang]

g_settings_get_string 

return a newly-allocated string

[lukefromdc]

I will remove the const qualifiers and free these when done, and deal with the preview initialization. A follow on PR will be ready shortly

[lukefromdc]

gtk_combo_box_get_active_id() does return a const gchar, so that's the apparent exception here

[zhuyaliang]

gtk_combo_box_get_active_id

The returned value is an interned string which means that you can compare the pointer by value to other interned strings and that you must not free it.

[lukefromdc]

Pr for working on this is at https://github.com/mate-desktop/caja/pull/1763