Skip to content
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

Close problem with Lazarus 1.6.4 #13

Closed
GitHubStefan13 opened this issue Apr 21, 2017 · 3 comments
Closed

Close problem with Lazarus 1.6.4 #13

GitHubStefan13 opened this issue Apr 21, 2017 · 3 comments

Comments

@GitHubStefan13
Copy link

GitHubStefan13 commented Apr 21, 2017

example

When you put the Interfaces after the Unit-Forms bgacontrols will cause a crash after you close the Programm(as seen in Picture)

Don't know if this is a problem with your Controls or Lazarus itself. Still thought its worth mentioning,
since i had no clue what caused the Problem.

Putting the Interface before the Unit-Form solves it though.

@lainz
Copy link
Member

lainz commented Apr 22, 2017

Hi, I can confirm that but I'm not sure if I understand why it happens. Well at least you found a way to solve it.

@GitHubStefan13
Copy link
Author

My theory is that Larazus destroys the Objects in the Order of the uses.
So first it destroys the Button in the Form-Unit after succesfully destroying it the object doesnt exist anymore but somehow Lazarus tries to destroy the Button in the Interface Unit again, thus the Access Violation on a non existing Object.

@lainz
Copy link
Member

lainz commented Apr 23, 2017

Ok. I will close it as we can do nothing to solve this.

@lainz lainz closed this as completed Apr 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants