FLTK logo

Re: DataReadyThread leak hunting in fltk 1.3.0-rSOMETHING

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.general  ]
 
Previous Message ]New Message | Reply ]Next Message ]

Re: DataReadyThread leak hunting in fltk 1.3.0-rSOMETHING "MacArthur, Ian (SELEX GALILEO, UK)" May 08, 2012  
 
> I have application that does have strange memory leak in Mac OSX 10.6.8
> and 10.7.3 but not leaking in Mac OSX 10.5.8. I've used valgrind to figure
> out where the leak happens and it points to
> DataReady::DataReadyThread(void*) report below the message. XXXX.... is
> name of my application.
> 
> I've been searching for the dependencies and one of the pieces in the
> puzzle is that there is much more leaks when to use Fl::wait(0.01) and
> less leaks when to use Fl::wait(0.1) resulting almost no leaks but
> valgrind still identifies leaks.


Something in Fl_cocoa.mm then? I don't know, code looks OK to me, but I am not at all good at objc so there maybe something... Manolo is possibly the best person to ask?






SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL
A company registered in England & Wales.  Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.