each time a managed window is iconized a new icon window is created and the previous one is lost. This window leak is a serious bug itself, but it may result in even more serious consequences. Each decoration window created by afterstep for an application window has an associated context, which is in fact a pointer to an aftrstep window, ASWindow, object. For leaked icon windows context is never destroyed leading to potential access to memory region that is not a valid ASWindow, if application for which icon windows were created is terminated. The latter usually results in coredump, symptom of which was desribed in PR ports/34066 How-To-Repeat: iconify/deiconify a window multiple times; using application based on XQueryTree on root window determine number of child-windows. it will be incremented after each iconification. Coredumps have a more probabilistic nature and usually happen if you have substantial number of leaked windows, their application is terminated and you havily use applications that create windows and then change their properties through configure requests, e.g. opening certain web-pages using netscape.
State Changed From-To: open->closed Committed, thanks!