-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate Carbon TTrayIcon leak #17
Comments
Some answers - May leaks be ignored? - No, absolutely not. http://forum.lazarus.freepascal.org/index.php/topic,38601.msg267243.html#new |
(the questions link to forum threads that answer them)
|
Just to get on record ... |
For the record it was suggested that to get offending line numbers on the Mac, it was necessary to recompile the RTL with debugging info. http://forum.lazarus.freepascal.org/index.php/topic,38917.0.html Its now agreed the problem (lack of suitable debugging info) is a deep seated one with the Mac FPC/RTL see https://bugs.freepascal.org/view.php?id=32775 Suggestions that the actual problem (leaks in TrayIcon) may never be fixed, its a Carbon issue and Carbon is headed fro the scrap heap. I have now made some changes to tomboy-ng so it builds and works under Cocoa but there are more leaks there. Same underlying issue, debugging tools don't report the source of leaks ! QT is reported to be better supported but our design goal here is to have a dependency free install. |
Some conclusions about how this leak affects this application.
Each call to InternalUpdate seems to leak about 80 bytes. Not a lot but it is a growing leak ! I don't like any of the above but do need a short term fix. Long term, the underlying Mac problem needs to be fixed but there does not appear to be a enthusiasm to do so, Apple's active discouragement of non endorsed products is an issue. After all, last thing Apple would support is a cross platform application... |
1 similar comment
Some conclusions about how this leak affects this application.
Each call to InternalUpdate seems to leak about 80 bytes. Not a lot but it is a growing leak ! I don't like any of the above but do need a short term fix. Long term, the underlying Mac problem needs to be fixed but there does not appear to be a enthusiasm to do so, Apple's active discouragement of non endorsed products is an issue. After all, last thing Apple would support is a cross platform application... |
The 0.12 release has some changes made, to mac only, that attempt to cut down on the number of times we update the RecentMenu items. Don't like it, its ugly and does not fully fix the problem but that might be all we see until we can move over to the Cocoa widget set. I see some progress happening there but its got a way to go. Last time I checked, we could compile to Cocoa but there were even more leaks and several other issues. But, as I said, a lot of effort is going into it right now. |
OK, Mac now does not use the leaky TrayIcon and, it seems is now leak free. Bonus is Mac now has a much more Mac like feel. If you like that sort of thing. |
To get the TrayIcon memory leak fixed in 1.8 the report should get more attention by adding more specific information like a trace or an example how to reproduce. Necessary information should be available via Leakview.
May leaks be ignored?
How to detect memory leaks in Lazarus
How to properly release memory
good example report with trace and patch
The text was updated successfully, but these errors were encountered: