The link on the home page needs to be updated, because it still points to 2.0.10.
So excited, I downloaded and installed it for my Mac (High Sierra), which it upgraded itself from Lazarus 2.0.11, ran my project and got told:
"cocoagdiobjects.pas(11,34) Fatal: Can't find unit CocoaGDIObjects used by CocoaPrivate"
So excited, I downloaded and installed it for my Mac (High Sierra), which it upgraded itself from Lazarus 2.0.11, ran my project and got told:Isn't 2.0.11 the branch from where 2.0.12 was built?
"cocoagdiobjects.pas(11,34) Fatal: Can't find unit CocoaGDIObjects used by CocoaPrivate"
Not a great start.
EDIT: Followed the instructions to completely remove Lazarus, then started again. Same error. Gone back to 2.0.11, which works fine.
I have two problems with the Win32 version:You can see the merged revisions here :
-The first is extremely annoying; but not a deal breaker: the Source Editor is quite sluggish, 2.0.10 wasn't when editing the same code base.
-It tends to hang when closing: when I first installed it and rebuilt it to install packages it refused to close until I forced it via Windows, and has refused every time I tried to get it to rebuild without hanging: I have to force it through Windows or Task Manager. It builds properly: the hang occurs when the IDE is closing itself to restart. The problem is also present, intermittently, when building any of my own code, those unlucky times when I close it the window goes away, but I can see the process wasting CPU cycles until I kill it with Task Manager or similar.
Isn't 2.0.11 the branch from where 2.0.12 was built?
They should be identical now.
Isn't 2.0.11 the branch from where 2.0.12 was built?
They should be identical now.
No idea. It's odd.
The strange thing is, it reported the error AND opened the unit it couldn't find!
Anyway: go to menu: Tools > Configure build lazarusYep, that did it...thank you.
Check: "Clean all"
Rebuild
See if that helps.
Thanks to the Lazarus development team for the latest release.Amen to that - in my opinion, although it lacks way behind Delphi (which obviously is a prohibitive cost for most of us), it is also way ahead of Delphi in having a native IDE for each platform - no more having to code on a Windows machine, then port across to a Mac (for example). Except for a few remaining projects I have in Delphi, I can't see myself going back.
Some of us are not that expressive and may not show up here often, but we really appreciate your work.
I have two problems with the Win32 version:You can see the merged revisions here :
-The first is extremely annoying; but not a deal breaker: the Source Editor is quite sluggish, 2.0.10 wasn't when editing the same code base.
-It tends to hang when closing: when I first installed it and rebuilt it to install packages it refused to close until I forced it via Windows, and has refused every time I tried to get it to rebuild without hanging: I have to force it through Windows or Task Manager. It builds properly: the hang occurs when the IDE is closing itself to restart. The problem is also present, intermittently, when building any of my own code, those unlucky times when I close it the window goes away, but I can see the process wasting CPU cycles until I kill it with Task Manager or similar.
https://wiki.lazarus.freepascal.org/Lazarus_2.0_fixes_branch#Fixes_for_2.0.12_.28merged.29
It is unlikely that any of those caused a big slowdown or hang. Such things have happened for unknown reasons also in the past.
I recommend you try Lazarus trunk. It is much ahead of fixes_2.0.x branch now. It also has some speed optimizations.
Soon a branch for 2.2 will be forked from it.
Thanks to the team for all the work and the new release. :)
I have two problems with the Win32 version:
-The first is extremely annoying; but not a deal breaker: the Source Editor is quite sluggish, 2.0.10 wasn't when editing the same code base.
-It tends to hang when closing: when I first installed it and rebuilt it to install packages it refused to close until I forced it via Windows, and has refused every time I tried to get it to rebuild without hanging: I have to force it through Windows or Task Manager. It builds properly: the hang occurs when the IDE is closing itself to restart. The problem is also present, intermittently, when building any of my own code, those unlucky times when I close it the window goes away, but I can see the process wasting CPU cycles until I kill it with Task Manager or similar.
Thanks to the team for all the work and the new release. :)
I have two problems with the Win32 version:
-The first is extremely annoying; but not a deal breaker: the Source Editor is quite sluggish, 2.0.10 wasn't when editing the same code base.
-It tends to hang when closing: when I first installed it and rebuilt it to install packages it refused to close until I forced it via Windows, and has refused every time I tried to get it to rebuild without hanging: I have to force it through Windows or Task Manager. It builds properly: the hang occurs when the IDE is closing itself to restart. The problem is also present, intermittently, when building any of my own code, those unlucky times when I close it the window goes away, but I can see the process wasting CPU cycles until I kill it with Task Manager or similar.
I can't reproduce it here.
But the symptoms description would make me thing, that the IDE is running some background task.
Some tasks in the IDE, take a long time, and do a lot of Application.ProcessMessages. The the rest of the IDE only works during those ProcessMessages, and the first thing you will note is the editor slows down.
Of course the background task could also prevent the IDE from exiting.... (maybe the task goes wrong, and loops forever)
Now one scenario with ProcessMessages it the Debugger (the gdb based one, not fpdebug). However that should play nice on exit. And also that has not changed between versions.
If you run "Search in Files" that could also happen.
But that are all scenarios that do not apply all the time, and that you need to trigger.
I saw another occurrence in CheckLfmDlg. Not sure when this happens.
And there may be more in other parts of the source.
Maybe codetools do some work.
Please start the IDE with --debug-log=c:\log.txt (or wherever you want the log).
Then submit this logfile.
With a bit of luck, maybe it contains a hint.
Thanks to the team for all the work and the new release. :)
I have two problems with the Win32 version:
-The first is extremely annoying; but not a deal breaker: the Source Editor is quite sluggish, 2.0.10 wasn't when editing the same code base.
-It tends to hang when closing: when I first installed it and rebuilt it to install packages it refused to close until I forced it via Windows, and has refused every time I tried to get it to rebuild without hanging: I have to force it through Windows or Task Manager. It builds properly: the hang occurs when the IDE is closing itself to restart. The problem is also present, intermittently, when building any of my own code, those unlucky times when I close it the window goes away, but I can see the process wasting CPU cycles until I kill it with Task Manager or similar.
I can't reproduce it here.
But the symptoms description would make me thing, that the IDE is running some background task.
Some tasks in the IDE, take a long time, and do a lot of Application.ProcessMessages. The the rest of the IDE only works during those ProcessMessages, and the first thing you will note is the editor slows down.
Of course the background task could also prevent the IDE from exiting.... (maybe the task goes wrong, and loops forever)
Now one scenario with ProcessMessages it the Debugger (the gdb based one, not fpdebug). However that should play nice on exit. And also that has not changed between versions.
If you run "Search in Files" that could also happen.
But that are all scenarios that do not apply all the time, and that you need to trigger.
I saw another occurrence in CheckLfmDlg. Not sure when this happens.
And there may be more in other parts of the source.
Maybe codetools do some work.
Please start the IDE with --debug-log=c:\log.txt (or wherever you want the log).
Then submit this logfile.
With a bit of luck, maybe it contains a hint.
I did some tests with the conditions you mentioned, haven't been able to hang the IDE after building several projects after using Search in files and running under the GDB debugger.
The consistent hang I can reproduce is after rebuilding the IDE: it managed to succesfully exit once, because the process only really linked, when I cleaned it and rebuilt it, it hanged again, I attach, as you requested, the log.txt file, such as it is: it just stops logging mid word.
The editor seemed responsive as usual again, so if the only problem is the IDE not killing itself properly when being rebuilt, it's no longer a deal breaker for me.
I hope some of this helps, and I'm very grateful for your assistance.
Sorry Martin, I think I answered in place of another user...Ups...
For the one build with gtk widgetset, In Window menu, going with the mouse pointer back an forth over the "Tabs for project(x)" option, the checkbox from its left gets checked at first pass, and unchecked at the second pass, without click, just passing with the pointer. I thought my touchpad is crazy so I installed an USB mouse. Same behavior.The chceckbox should indicate the active tab. So if the tab did not change...
I did some tests with the conditions you mentioned, haven't been able to hang the IDE after building several projects after using Search in files and running under the GDB debugger.
The consistent hang I can reproduce is after rebuilding the IDE: it managed to succesfully exit once, because the process only really linked, when I cleaned it and rebuilt it, it hanged again, I attach, as you requested, the log.txt file, such as it is: it just stops logging mid word.
I guess these "deprecated" tags slipped into v2.0.12 by accident. The events that you mention are related to new features which will be in the product in v2.2, and the deprecated events/methods/properties will be removed in Laz 2.3
I did some tests with the conditions you mentioned, haven't been able to hang the IDE after building several projects after using Search in files and running under the GDB debugger.
The consistent hang I can reproduce is after rebuilding the IDE: it managed to succesfully exit once, because the process only really linked, when I cleaned it and rebuilt it, it hanged again, I attach, as you requested, the log.txt file, such as it is: it just stops logging mid word.
"it just stops logging mid word"
And that is in the middle of compiling. Unless there is a big chunk of the log, that was not written to disk.
When it happens again, look at the title of the IDE main window (the window with the menu): It should still say "compiling", and the "red square >stop< button" should still be active.
If that happens, and there is no progress in the "messages" windows, then open the task monitor, and check if there is any fpc.exe and/or ppc___.exe (depending on bitness that is ppci386.exe or ppcx86.exe or ...)
If it does not say "compiling", (and the red button is disabled) then it finished compiling, and it should try to restart.
If it hangs during restart => you can test that by going to Tools > "Configure build lazarus" and un-check the "restart after building IDE" checkbox. (Then you have to restart yourself at some point).
You can build your IDE with -WC (specified in "Configure build lazarus"). Then do not use --debug-log.
The IDE will now open with a console window, and all logging happens there. This often has less caching going on, so more of the log-output may be seen. But I would check the above things first.
Last not least.
The IDE has a feature to check if it is running. Even if switched off, it still does some check...
If the IDE hangs during startup, check in the task manager how many lazarus.exe and how many startlazarus.exe there are.
You can also locate your temp folder e.g. C:\Users\USERNAME\AppData\Local\Temp
and (when the IDE is NOT running) delete all files *_LazarusMain*
I now looked at it in more detail and cannot find a difference between 2.0.10 and 2.0.12 regarding these events... Both versions do have a TChartAxis.OnMarkToText, but no OnGetMarkText, and there is no "deprecated" message here either.
Did you open your project with Lazarus trunk in between? It is clear that the new version can introduce new properties and events, and when you return to a release version they can lead to issues.
Yes, on february 21, I pulled the svn of the then pre-production v2.0.12 as my contribution to test it.You accidentally pulled Lazarus trunk (development version). That is my guess anyways.
For 2.0.10 I made a little script containing the necessary modifications (s. attachments). If I apply the same modifications for 2.0.12, everything is working as expected.
When testing my applications with the new release (macOS s.b.), I noticed just these same problems as for 2.0.10:
- OpenSSL: connect to some websites fails
- Application does not start from IDE
slow editor32 or 64 bit / Windows version?