After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 334137 - misc libwnck fixes
misc libwnck fixes
Status: RESOLVED FIXED
Product: libwnck
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: libwnck maintainers
libwnck maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-10 14:50 UTC by Dan Winship
Modified: 2006-03-25 08:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (1.20 KB, patch)
2006-03-10 14:51 UTC, Dan Winship
committed Details | Review

Description Dan Winship 2006-03-10 14:50:57 UTC
Here are two leak fixes in tasklist.c and a branch-result-depends-on-
uninitialized-memory fix for xutils.c. (The specific problem is that
icon_cache->prev_mask doesn't get initialized, but really, if God had
meant for us to initialize variables to 0 one-by-one, he wouldn't have
given us g_new0.)
Comment 1 Dan Winship 2006-03-10 14:51:22 UTC
Created attachment 61039 [details] [review]
patch
Comment 2 Elijah Newren 2006-03-10 19:19:13 UTC
Sweet, thanks for catching this.  Is this causing any big issues, or should we just wait until after 2.14.0 to avoid the need to get approval to break hard code freeze?  Also, for future reference, could you use the -p flag when creating patches to make it easier for me to read them?  Thanks.
Comment 3 Dan Winship 2006-03-10 20:29:12 UTC
The downstream bug is https://bugzilla.novell.com/show_bug.cgi?id=78329.
(His comment that he's only using the Window Selector is probably mistaken;
the other three all run on the bottom panel by default and he probably
didn't realize that counted as part of the panel too.)

He's seeing a huge leak. I'm not sure that the leaks I fixed are large enough
to be the source of his problems, and I haven't heard back from him yet on
whether or not my patch fixes it for him. So there may be further patches.
At any rate, it's an old problem, so probably not freeze-break-worthy.

(The uninitialized variable part doesn't cause any problems that I'm aware of,
it's just something valgrind pointed out while I was searching for the leaks.)