sugest to avoid to memory leak

[MatejMagat305]

avoid memory leak resume and sugest to avoid to call GO functions for empty life cycle functions ...

[coveralls]

coverage: 66.487% (-0.003%) from 66.49% when pulling b161fcd on MatejMagat305:patch-1 into ecb8c1a on fyne-io:develop.

[andydotxyz]

I'm not sure about the way that some callbacks are deleted and others moved.

Why not make the PR just about the memory leak fix?

[MatejMagat305]

I'm not sure about the way that some callbacks are deleted and others moved.

Why not make the PR just about the memory leak fix?

this lines: https://github.com/fyne-io/fyne/pull/4118/files#diff-86b6487000ebad8b8c46272d0aa615cdbec1dba15013d82bed007ffa593e5464R90 is memory leaks, others are only therefore nothing theese functions do and call GO from C is recomended to eliminate ...

[Jacalz]

But you have, as stated in #4118 (comment), removed one of the functions. Why?

[andydotxyz]

I think I see why it looks inconsistent - because the onResume was written in C to do something but not in Go. But it was called processOnResume (so that the Go callback names were consistent). If that was renamed to onResume in the C file then I think we would have a consistent code and this could be approved.
Is that OK @MatejMagat305 ?

[MatejMagat305]

ok

[Jacalz]

Why did you close it? Andy just suggested changes

[MatejMagat305]

ach soory, I will changes tomorow

[andydotxyz]

Thanks for making these optimisations

[Jacalz]

Thanks. If there are more places where we are passing Go functions back into C, we probably want to remove those as well some time in the future. It is quite slow from what I have understood (but a lot faster in Go 1.21).

[MatejMagat305]

Thanks. If there are more places where we are passing Go functions back into C, we probably want to remove those as well some time in the future. It is quite slow from what I have understood (but a lot faster in Go 1.21).

well there are some functions like onContentRectChanged or onNativeWindowCreated, which are empty, but I did not know which one will you plan use ..., life time I dare move because I saw that life time are binding with running loop (are call from other way ...)