Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2000-08

Newbie bad installation

4 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Marc Weustink
to Bertil Wergelius: I have downloaded and installed latest fpc snapshot (Linux). Extracted lazarus.zip and…
Bertil Wergelius wrote
I have downloaded and installed latest fpc snapshot (Linux). Extracted lazarus.zip and runned make, make install.

OK, you didn't have to run make install, but it doesn't matter.

When I try to run the lazarus execute it won't start and if I try to run it from a terminal there are error messages about GTK objects.

You indeed need to run Lazarus from a console, the GTK messages you can safely ignore. But what are the last lines you see ?

Marc

Reply by email

Bertil Wergelius

I have downloaded and installed latest fpc snapshot (Linux). Extracted lazarus.zip and runned make, make install. When I try to run the lazarus execute it won't start and if I try to run it from a terminal
there are error messages about GTK objects.
I'm running this on Mandrake 7.0 which have Gtk+ version 1.2.6-6mdk. Can anyone help me with this, please.

Reply by email

Marc Weustink
to Marc Weustink: OK, you didn't have to run make install, but it doesn't matter. You indeed need to run…
Bertil Wergelius wrote
I succeded to start lazarus from the console but it keeps nagging about Gdk critical etc. It also seems to leak memory ; when I quit lazarus a message about 105 unreleased something. Can I safely ignore these also?

Yep, To emulate the devicecontexts and gdiobjects delphi uses to draw items, the GTK implementation of the LCL keeps track of these. In windows if you create and object (like a bitmap) you have to destroy it when you no longer need it. The message you see in the end is a counter on how many objects still exist.
AFAIK gtk will clean them when you exit the app. So there should be no memory leak if yo comapre it to before and after the app running. During the lifetime of the app you indeed can see this as a memoryleak. Running Lazarus for a while will result in over 5000 unreleased gdiobjects, you can imagine if you use Lazarus longer that at a certain point you are out of memory.
For now as long as Lazarus doesn't dump, you can ignore messages, since some object are created while they shouldnt and not all the cleanup code is present.

Marc

Reply by email

Bertil Wergelius
to Marc Weustink: OK, you didn't have to run make install, but it doesn't matter. You indeed need to run…

I succeded to start lazarus from the console but it keeps nagging about Gdk critical etc. It also seems to leak memory ; when I quit lazarus a message about 105 unreleased something.
Can I safely ignore these also?

Bertil

Marc Weustink wrote 13 lines
>When I try to run the lazarus execute it won't start and if I try to >run it from a terminal there are error messages about GTK objects. You indeed need to run Lazarus from a console, the GTK messages you can safely ignore. But what are the last lines you see ? Marc _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email