[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 150) Is this a memory leak in the X11R4 XtDestroyWidget()?!
Next Document: 152) Why does the process size of my X programs go up,up,up?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 150) Is this a memory leak in the X11R4 XtDestroyWidget()?!
Next Document: 152) Why does the process size of my X programs go up,up,up?
151) Is this a memory leak in the X11R4 deletion of work procs?!
Apparently the X11R4 NextEvent.c`CallWorkProc fails to properly replace
the work proc record back on the free list correctly.
if (delete) {
w->next = freeWorkRecs;
freeWorkRecs = w->next; /* should be =w; */
}
Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 150) Is this a memory leak in the X11R4 XtDestroyWidget()?!
Next Document: 152) Why does the process size of my X programs go up,up,up?
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
faq%craft@uunet.uu.net (X FAQ maintenance address)
Last Update October 22 2009 @ 05:36 AM