Will we ever see Delphi IDE working decently?
Will we ever see Delphi IDE working decently?
In Delphi Berlin (latest update) I get tons of "Internal Error" while building my projects forcing me to close and open Delphi constantly.
In Delphi Tokyo (latest update) I get "Embarcadero Debugger Kernel stopped working" errors followed by a "disconnected session" error while debugging my projects, again forcing me to closing and opening Delphi constantly.
Also Code Insight hangs the IDE constantly too, while it works flawless in Berlin.
It's almost impossible to work like this.
Anyone else here with this kind of issues?
Any solution for this?
Thanks!
In Delphi Berlin (latest update) I get tons of "Internal Error" while building my projects forcing me to close and open Delphi constantly.
In Delphi Tokyo (latest update) I get "Embarcadero Debugger Kernel stopped working" errors followed by a "disconnected session" error while debugging my projects, again forcing me to closing and opening Delphi constantly.
Also Code Insight hangs the IDE constantly too, while it works flawless in Berlin.
It's almost impossible to work like this.
Anyone else here with this kind of issues?
Any solution for this?
Thanks!
/sub
ReplyDeleteI may be the lucky one, but I don't see any of this on Berlin.
ReplyDeleteI occasionally have problems with 10.2.2 but not so that it significantly impacts my work, so can't say that I am affected in the same way as you.
ReplyDeleteI have same problems here (now) with Tokyo but with Berlin the problems where the same. At least 3/4 time per hour the IDE need to be closed/opened because code completion stop working, because syntax highlight stop working, because ctrl-click stops working, because of strange crashes, because if I try to compile several projects in a project group the IDE tell me something about incompatibility with dfm !?!? for a project that copile fine once the IDE is restarted.
ReplyDeleteI've to say that this kind of problems are increased tenfold if I'm heavily working on my runtime libraries and need often to recompile several projects to test the job done. In these situations working is becaming a nigthmare. If I'm focused on a single project and work only on it the environment seems more stable... I'm using only VCL win 32 projects for now.
Berlin seems stable for me but I only do vcl work.
ReplyDeleteDavide Angeli Disable Error Insight. It's super buggy
ReplyDeleteDavide Angeli I am having the code completoin lockup fairly regularly. By hitting "Esc" quickly a few times I can sometimes stop the IDE hanging altogether....
ReplyDeleteJohn Kouraklis ok I could disable it but it should not be the solution and we should not accept these solutions anymore.
ReplyDeleteOn these issues the answer is quite often "ok it is buggy what's the problem? disable it". If my customers tell me that my program is buggy the only thing that I could do is to solve the bugs! The solution is not to cover everything with layers of make-up. I don't know in which version error insight was introduced (maybe 1,2,3,4,5,6,7,8,9,10 versions ago?). At that time it could be buggy because it was a new feature...but now? What they did to improve this?
Davide Angeli I totally agree with you. If something is buggy it is a problem...well...by definition :-) And of course EMB should have done something about it long time ago
ReplyDeleteIDE pretty stable for me. I have no IDE add-ins and only 2 component libraries.
ReplyDeleteI will say Berlin was kind of stable, and Tokyo so far is being an improvement over it. I use CnPack, GExperts, Error Insight(on, finally), DevExpress, Jvcl/jcl, RO integrations.
ReplyDeleteI only do VCL Win64/Win32 and usually with only one project loaded.
ReplyDeleteA few years ago I used project groups with many projects, but was a nightmare also.
I don't know how it behaves with FMX and mobile development but I suspect it might be even worse.
This is a shame. I just payed €1000 to renew my subscription and get the latest updates, but things don't get any better.
Every release fixes a few bugs and introduces many more.
And this is going for several years now.
For how long and how much money can/will we all throw at Embarcadero until this gets fixed?
Everyday I loose 1 or 2 hours just to close and open Delphi again and again. It's 1 or 2 hours that I could be doing something useful.
Years go by and the frustrations keep growing. :(
Luis Madaleno That really does seem like you are struggling. Have you excluded the possibility that it is a third party component causing all of your troubles? I believe you can install MadExcept so that it captures IDE exceptions as well, so it may help you identify this.
ReplyDeleteThough a bit out of date, the following post may also give you some hints that will allow you to identify the source of your problem and then you could report it to Embarcadero, once you find a way of consistently repeating the problem.
https://delphicodemonkey.blogspot.co.uk/2015/12/how-to-find-and-fix-problems-in-your.html
May I ask those that experience instabilities (especially with the compiler getting stuck into some internal errors causing the IDE to crash or having to be restarted): Is your code using generics? Is your code using circular unit dependencies (circular by uses in implementation sections)? Are you using code completion (like ctrl+space for method/member suggestions)?
ReplyDeleteStefan Glienke my code use generics and there are circular unit dependancies by uses in implementation sections
ReplyDeleteStefan Glienke generics yes.
ReplyDeleteIn Berlin Code Insight is instantly and in Tokyo takes several seconds when it doesn't hang the IDE. All with the same project.
But my major issues with Tokyo started only after this last update.
Before that it worked pretty well.
Martyn Spencer Everything is possible.
ReplyDeleteI use a lot of third party controls. Full DevExpress, some TMS, among others.
It's almost impossible to check them all.
I will try MadExcept to see if it helps.
Thanks.
Luis Madaleno I use quite a few as well as DevExpress, though not TMS. You're right that it is a significant task to check all, but by debugging the IDE you may well gain some insight. Good luck!
ReplyDeleteChanged debug in Tokyo from 64bits to 32bits and its stable.
ReplyDeleteI'm usually getting access violation when closing the IDE. Needless to say that all insight stuff are broken. I agree with you, it's a pity that all these bugs remains for more than a decade...
ReplyDeleteI am annoyed when WE need to debug the IDE....
ReplyDeleteStefan Glienke yes, yes and yes.
ReplyDeleteStefan Glienke Generics and circular dependencies (but not too much). Class completion is totally broken by [unsafe] and [weak] attributes (if you use them for local variables).
ReplyDeleteCompiling for Android if some deeper dependency unit is edited almost certainly fails with weird linker errors. IDE must be restarted after that. Complete build is necessary, and it takes ages to rebuild. iOS debugging works once for every 20 tries... actually, I can't remember when was the last time I actually managed to debug on iOS. Debugging on Android mostly works, but it likes to lose connection or IDE just hangs. Complete restart of development machine together with Android device is usually necessary for debugging to start running again.
AV on closing is almost mandatory.
Dalija Prasnikar So, the IDE everyone wants to buy and use.
ReplyDeleteDelphi is broken is many ways. It's a mess. A sad mess.
I changed my project target platform from 64bits to 32bits and in Tokyo things now work better.
ReplyDeleteThe debugger doesn't crash and code insight works, although not as fast as in Berlin.
So this is definitely a problem with this latest Tokyo release.
Davide Angeli It doesn't matter once you have a project group loaded and are switching between pre-compiled and compiled files everything eventually goes FUBAR. This changes depending on IDE release but its always there. It leaks into Build Groups and while much better in Berlin 2 the original Tokyo release broke all that again. This very same issue doesn't allow debugging and has the Blue dots disappear, its all folder/file/compiled/source code stuff because when you button down the IDE Library paths and only work on a small subset all works. However the fact that in one Release its almost acceptable only to come back in the next makes all this typing worthless :)
ReplyDeleteDalija Prasnikar These problems I also encountered while trying to build an iOS app made me realize it was just easier to use Apple's tool. Any gains I would get with FMX get negated by tooling and framework bugs.
ReplyDeleteMike Margerum I went with native solutions for other reasons.
ReplyDeleteBut, generally all obstacles have cumulative effect and might drive developers away from particular development tool.
Having said that all other tools are also far from perfect. So it is always about finding the right balance and choosing the right tool for the job. Usually, that means the tool that will give you the least trouble in completing particular project.
Stefan Glienke " Is your code using generics? Is your code using circular unit dependencies...? Are you using code completion...?"
ReplyDeleteHave you recently smelled something that could best be described as fudge when there is no fudge?
(Obscure "Warehouse 13" reference :-) )
/sub
ReplyDeleteDalija Prasnikar I had other reasons as well including already having work on iOS for 7 years. My first (now 8 yo) project just keeps on running. Ive upgraded Xcode dozens of times and never had it maul my project file and i've had very little in the way of changes required to keep it going. Swift. now thats a different story... heh
ReplyDeleteThat will not get better. Emba has fired the entire IDE team. There is no one left to develop and correct bugs. P.S. I only work with Notepadd ++. Everything is so easy with it. At night everything is compiled with a build software autmatically.
ReplyDeleteTried Visual Studio Code with OmniPascal extension and it works pretty well. And code completion works very fast.
ReplyDeleteAnyone here already tried this?
My projects are mostly small, I don't have such bugs
ReplyDelete