bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #23233] SVN version breaks GWorkspace.app


From: Fred Kiefer
Subject: [bug #23233] SVN version breaks GWorkspace.app
Date: Mon, 12 May 2008 10:25:00 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

Update of bug #23233 (project gnustep):

                Category:                    None => Gui/AppKit             
              Item Group:                    None => Bug                    
             Assigned to:                    None => FredKiefer             

    _______________________________________________________

Follow-up Comment #1:

Looks like I did cause this by a memory leak fix on NSWindow. There the
graphics context kept a reference of the window in its attributes dictionary
and the window itself had a reference on the graphics context. This resulted
in both never being freed.
I resolved this by reducing the retain count of the window after the graphics
context gets created and increasing it just before the graphics context for
the window is freed.
What I don't see is how this correction should result in a segmentation fault
in GWorkspace. There is either an error in my change or the code in GWorkspace
was always incorrect, but the problem was hidden by the gui bug. And of course
there are plenty more possibilities.

Could you please try to find out, which sort of window is causing this? I am
currently away from my home computer and so it is hard for me to find out
where a GSContext gets autoreleased and what GSIMaps a context keeps.

You should try to use all the build in memory debugging facilities of GNUstep
like enableDoubleReleaseCheck: and all the rest I don't remember :-)

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?23233>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]