Haven't noticed the same, just did a couple of hours of debugging / fixing in a single session, and it's sitting there idling with zero CPU usage and <200MB ram used. Though it was a console application, so no visual stuff involved.
Oh hello. I left it idle for a couple of hours to watch a movie, and when I came back it was definitely very sluggish, with the mouse cursor lagging every second or so.
For me is not a news of the update 1. I already noticed this in the original D10 installation. After installing upd1 I'm not experiencing improvments but also the things are not getting worse. Sometimes IDE is terribly slow or completely locked for a lot of seconds. XE8 was not affected by these problems.
While it would be worth opening an issue in any case, even better if there is a way to add some more substance to it. With some specifics, we could go over the list of fixed issues and see if any of those could cause a regression (from 10 Seattle RTM).
In this threads there are references to debugging, leaving the IDE idle a couple of hours, and different scenarios... while others say they din't notice a real difference (myself included).
Same issue here. And again it seems that we have reached the "good old" 'cannot reproduce, ticket closed' problem. Marco Cantù , saying quite frankly and with good intentions - your (Embarcadero's) testing is definitely not good.
Primož Gabrijelčič If we gather enough information we can investigate. For example, the slow down IDE opening seems to be affected by network connection / OS / VM combination and is being investigated. If the "same issue" refers to the welcome page slowing down things, it can be investigated (but need to be opened first ;-). If there are other specific circumstances, let us know. Testing is not good <> we should test more combinations of hardware / OS / VM. If we figure out what's up, we'll add those scenarios to our testing.
Hi Marco Cantù - I'm not running in a VM and I don't have the welcome page open, but I still experience IDE gradually slowing down the longer I use it. Nothing like the old memory problems, but eventually the IDE still crashes. This never happened before update 1. It's a strange kind of slow down though. It seems like the cursor becomes more and more laggy and general IDE interaction become less responsive e.g. clicking menus, scrolling the editor etc. Restarting the IDE always fixes the problem for a while.
Paul Thornton Same here, not seems related to welcome page. Running the project without debugging helps to delay the issue. When it gets laggy its like a slow old pc or an excessive repaint/invalidate problem, but the cpu and memory usage in process explorer is very small. Strange.
David Berneda Paul Thornton Attila Kovacs Primož Gabrijelčič Stefan Glienke Are you working on Windows 10 machine? I'm not sure but I suspect that this kind of slowdown could be related to some background system process (maybe memory manager?). After working for a while in my Win10 machine with D10 I could see in the task manager the SYSTEM process occupy 13% of processor (i7 with 8 core) and it progressively consume over then 1Gb of RAM (without stop). Yesterday I had to restart Window to stop that memory consumption. In addition to Delphi IDE I've opend only MS Outlook 2015 and Google Chrome.
Davide Angeli Yes, on WX. But Delphi starts working fine (for the next hour) if I restart the BDS. And this didn't happen in original Delphi 10. And WX works just OK if I don't use Delphi.
It is worse on my side - when Delphi starts slowing down, my whole system starts behaving slow, too. Even mouse cursor moves with a delay. Then I stop Delphi and everything works fine again.
Primož Gabrijelčič Attila Kovacs You are right. I'm in your same situation now: all system is slowing down. I'm trying to read mails with outlook and changing from a folder to another it tooks a couple of seconds. Closed the Delphi IDE and things works fine again.
Thanks for the further information, we'd investigate. Still not sure if anyone opened a QC report... but I think we are tracking it internally at this point
After some investigation with procmon etc, just dragging around the ide window (not maximized), I got a GDI "out of resources" with trace from VirtualTreeView ide repaint steps. Not sure this is the real cause but fits with the symptoms.
I use procexplorer as a replacement for Taskmanager, but it can also display GDI objects. I'm more sure now the reason is unreleased handles, just dragging the ide or debugging is losing aprox 100 gdi objects per second. Also when debugging F7, F8 steps etc.
I confirm the GDI handle increase. I started with 1800 and now after an hour of working it has reached 4700. When I closed the IDE the last time because of the slowness it was almost 7000. In my case it's enough minimize and maximaze the ide to loose dozens of GDI handles.
Now if the IDE would not just die because of that retarded copy protection when I replace the borlndmm.dll with the one from FastMM and put the FastMMFullDebug along with it... *frustrated*
Attila Kovacs I just continued the investigation and turned off plugins until the issue disappeared :) The hint with the object inspector was very helpful for reproducing it.
Stefan Glienke Thank you, very much! Marco Cantù, can you please reroute the support money we are paying you to Stefan and Andy and all the great guys that solve problems instead of you?
Haven't noticed the same, just did a couple of hours of debugging / fixing in a single session, and it's sitting there idling with zero CPU usage and <200MB ram used. Though it was a console application, so no visual stuff involved.
ReplyDeleteI also felt that the IDE was getting a little slower. I never felt that before update 1.
ReplyDeleteOh hello. I left it idle for a couple of hours to watch a movie, and when I came back it was definitely very sluggish, with the mouse cursor lagging every second or so.
ReplyDelete/sub
ReplyDeleteFor me is not a news of the update 1. I already noticed this in the original D10 installation. After installing upd1 I'm not experiencing improvments but also the things are not getting worse. Sometimes IDE is terribly slow or completely locked for a lot of seconds. XE8 was not affected by these problems.
ReplyDeleteI also noticed this today after installing update 1 - this really needs to get fixed! Did anyone already open an issue? Marco Cantù FYI
ReplyDeleteWhile it would be worth opening an issue in any case, even better if there is a way to add some more substance to it. With some specifics, we could go over the list of fixed issues and see if any of those could cause a regression (from 10 Seattle RTM).
ReplyDeleteIn this threads there are references to debugging, leaving the IDE idle a couple of hours, and different scenarios... while others say they din't notice a real difference (myself included).
Looks like I have a similar issue: https://plus.google.com/+UweRaabe/posts/aohvL4QfgxM
ReplyDeleteAs a workaround just close the welcome page.
Same issue here. And again it seems that we have reached the "good old" 'cannot reproduce, ticket closed' problem. Marco Cantù , saying quite frankly and with good intentions - your (Embarcadero's) testing is definitely not good.
ReplyDeletePrimož Gabrijelčič If we gather enough information we can investigate. For example, the slow down IDE opening seems to be affected by network connection / OS / VM combination and is being investigated. If the "same issue" refers to the welcome page slowing down things, it can be investigated (but need to be opened first ;-). If there are other specific circumstances, let us know.
ReplyDeleteTesting is not good <> we should test more combinations of hardware / OS / VM. If we figure out what's up, we'll add those scenarios to our testing.
Hi Marco Cantù - I'm not running in a VM and I don't have the welcome page open, but I still experience IDE gradually slowing down the longer I use it. Nothing like the old memory problems, but eventually the IDE still crashes. This never happened before update 1. It's a strange kind of slow down though. It seems like the cursor becomes more and more laggy and general IDE interaction become less responsive e.g. clicking menus, scrolling the editor etc. Restarting the IDE always fixes the problem for a while.
ReplyDeletePaul Thornton Same here, not seems related to welcome page. Running the project without debugging helps to delay the issue. When it gets laggy its like a slow old pc or an excessive repaint/invalidate problem, but the cpu and memory usage in process explorer is very small. Strange.
ReplyDeleteDavid Berneda - Yes, I forgot to mention the the memory and CPU usage are pretty normal for me too.
ReplyDeleteDavid Berneda Paul Thornton Attila Kovacs Primož Gabrijelčič Stefan Glienke Are you working on Windows 10 machine? I'm not sure but I suspect that this kind of slowdown could be related to some background system process (maybe memory manager?). After working for a while in my Win10 machine with D10 I could see in the task manager the SYSTEM process occupy 13% of processor (i7 with 8 core) and it progressively consume over then 1Gb of RAM (without stop). Yesterday I had to restart Window to stop that memory consumption. In addition to Delphi IDE I've opend only MS Outlook 2015 and Google Chrome.
ReplyDeleteDavide Angeli Yes, on WX. But Delphi starts working fine (for the next hour) if I restart the BDS. And this didn't happen in original Delphi 10. And WX works just OK if I don't use Delphi.
ReplyDeleteDavide Angeli Nope, 8.1
ReplyDeleteOk it's not a SysOp problem
ReplyDeleteIt is worse on my side - when Delphi starts slowing down, my whole system starts behaving slow, too. Even mouse cursor moves with a delay. Then I stop Delphi and everything works fine again.
ReplyDeletePrimož Gabrijelčič Attila Kovacs You are right. I'm in your same situation now: all system is slowing down. I'm trying to read mails with outlook and changing from a folder to another it tooks a couple of seconds. Closed the Delphi IDE and things works fine again.
ReplyDeleteThanks for the further information, we'd investigate. Still not sure if anyone opened a QC report... but I think we are tracking it internally at this point
ReplyDeleteAfter some investigation with procmon etc, just dragging around the ide window (not maximized), I got a GDI "out of resources" with trace from VirtualTreeView ide repaint steps. Not sure this is the real cause but fits with the symptoms.
ReplyDeleteI use procexplorer as a replacement for Taskmanager, but it can also display GDI objects.
ReplyDeleteI'm more sure now the reason is unreleased handles, just dragging the ide or debugging is losing aprox 100 gdi objects per second.
Also when debugging F7, F8 steps etc.
Useful feedback, thanks. Looking into it ASAP, although we'll have to wait until Thanksgiving for some of the US developers to get back to work...
ReplyDeleteI cannot confirm the handle thing. It sits at 1400-1500 here and does not increase (did a bit debugging, opened and closed some projects, recompiled)
ReplyDeleteI confirm the GDI handle increase. I started with 1800 and now after an hour of working it has reached 4700. When I closed the IDE the last time because of the slowness it was almost 7000. In my case it's enough minimize and maximaze the ide to loose dozens of GDI handles.
ReplyDeleteAttila Kovacs Forget it, I was stupid and watched handles instead of GDI objects. Can confirm now, its going up and at 10k it crashes.
ReplyDeleteNow if the IDE would not just die because of that retarded copy protection when I replace the borlndmm.dll with the one from FastMM and put the FastMMFullDebug along with it... *frustrated*
ReplyDeleteAttila Kovacs How much time it will take depends on the nature of the issue... it is hard to know at this point. We'll keep you posted.
ReplyDeleteFound the bugger: ModernTheme230.bpl
ReplyDeleteRemove that from "HKEY_CURRENT_USER\Software\Embarcadero\BDS\17.0\Known IDE Packages" and leaks are gone.
Reported: https://quality.embarcadero.com/browse/RSP-13023
Marco Cantù Allen Bauer Luis Navarro FYI
Attila Kovacs I just continued the investigation and turned off plugins until the issue disappeared :) The hint with the object inspector was very helpful for reproducing it.
ReplyDeleteStefan Glienke Thank you, very much! Marco Cantù, can you please reroute the support money we are paying you to Stefan and Andy and all the great guys that solve problems instead of you?
ReplyDeleteStefan Glienke Thanks a lot for the detailed bug report. Really appreciated.
ReplyDeleteAttila, this community is really fast :-) good catch !
ReplyDeleteFYI, http://cc.embarcadero.com/item/30453
ReplyDelete