GNOME Bugzilla – Bug 721039
ShellAppSystem: own the memory for the startup wm class and app id
Last modified: 2013-12-26 22:45:24 UTC
Fixes the recognition of epiphany web applications (which use StartupWMClass to override the fact that wm_class_instance is epiphany)
Created attachment 264884 [details] [review] ShellAppSystem: own the memory for the startup wm class and app id The hash table must keep a copy of the IDs, because the GAppInfos are unreferenced (and thus freed) at the end of the function. This was possibly not a problem if the GAppInfos were referencing the memory-mapped cache, but it becomes one for regularly parsed desktop files in ~/.local.
Review of attachment 264884 [details] [review]: But we ref the GAppInfo when we save it in the ShellApp, no?
(In reply to comment #2) > Review of attachment 264884 [details] [review]: > > But we ref the GAppInfo when we save it in the ShellApp, no? No, it's a different GAppInfo, used only for the StartupWMClass scan.
Review of attachment 264884 [details] [review]: Oh, right, since ShellApps are created "lazily" now, the scan will unref the GAppInfo.
Attachment 264884 [details] pushed as f3feb13 - ShellAppSystem: own the memory for the startup wm class and app id