Method Design Screen Issue

No, I haven't reproduced it yet.

I would like to make an observation on this. I don't believe it has anything to do with time or size. In my case I have observed that the more complicated my code gets, the slower intellisense and typing in general gets. I think it has to do with how much intellisense has to keep reading the code to catch the references, ie button clicks, filters, onchange events and so on. So with every key click it has to cycle more and more, eventually bogging down to almost a standstill. If I generate a basic CRUD page and begin to edit it, it goes quite quickly until the code begins to get more complicated and then it begins to slow down. Not sure if it's a memory leak or just to much information to buffer. Anyway just my observation, but it definitely does slow down as the page gets more complicated.

Hi @daveg1466,

Do you have an app where this issue is reproduced? I would love to test it so we have a chance to fix this problem once and for all.

The complexity seems meaningful but it's not explaing excatly the stuation itself (for my oppinion).

I designed many test to reproduce the issue. But I couldn't write a good stepped reproduce process. Some of them the only one paged test projects and they started the slowing effects. These were very basic non complex projects.

I can't exclude the time variable totaly. Because I have keept open some project when I working in normal speed. When I return to my code the slowing effect was active.

I'm totaly working hibrit mode now using RBS's versitality. I use the all design feautres from the RBS and the coding features from VS Studio. I'm dreaming working in RBS with the all features but this is good enough for me until resolve this issue. So I stopped design new tests when a new bright idea :slight_smile:

I do, would you like me to send it to you? Do you need a copy of the sql database as well?

Sure! Also tell me what to do in order to reproduce the slowness - which file to open and what changes to make.

This should be required unless I have to run the application. In that case you can send us the SQL CREATE script of the database.

@korchev,

I think you don't have good news yet about the slow-motion issue. Do you have any progress in reproducing the issue?

I am afraid no. We haven't reproduce this issue yet regardless of what we try.

Hi @korchev,

Thank you for your answer. I have a suggestion for this issue. I know that many times my suggestions do not fit your priority goals. I can understand your efforts and please you understand me. I only dream that I use RBS as the only development tool for my processes.

Anyway...

The current situation.
When I face the slow motion issue, the only way for me to continue my work is to restart the RBS and reload the solution, open the working pages and files. I stubbornly resist using VScode or VS Studio to edit the codes. (Because design processes are not slowing.)

The suggestion.
Is it possible to before the concrete solution a simple refresh button? When the developer clicks it RBS will take a breath, restart itself, load the current project, and open the current pages. This is what I do manually. It could be a selfish request.

Hi @koksal.basar,

We prefer not to implement such workarounds for an actual issue. I am positive we would reproduce it at some point and find what is causing it. I will update this thread as soon as this happens. Meanwhile we would be grateful if any member of the community can help us reproduce this problem in a test app.

With today's release (1.16.0) we shipped a fix to a performance issue which sounds similar to the one discussed in this thread. The code editor and the rest of the UI become laggy in certain conditions. The problem we fixed was caused by having a lot of items in the file explorer tree.

In our test case the problem appeared when a directory that contained 2300 files was expanded in Radzen Blazor Studio. This caused enormous lags - for example new characters appeared a few seconds after typing them. When the directory was collapsed everything went back to normal.

We believe v1.16.0 fixes this issue and hope it was the same thing @koksal.basar and @daveg1466 (and probably others) are experiencing.

2 Likes

Just to report. The issue seems to be significantly less since this update. I will continue to monitor it and keep you up to date! Thank you very much for your attention to this problem!

Hi @korchev,

At this moment I can not say except "thank you for your efforts". The coding experience is much much better.

Update:20231025

The lag has not absolutely eliminated. The response time is a little bit faster but not fluent. Intellisense needs CTRL + Space many times and shows a "Loading..." message generally.

That's unfortunate. If you have any new instructions how to reproduce let us know. Also do you have a lot of nodes expanded in the tree when the lag happens? Is the project running? Does it behave better if you stop the project?

I do not have any special instructions about reproducing the issue. I worked for a couple of hours without issue. Then saved my project but I didn't close the RBS as I used to. When I started to work today it was laggy. Nobody touched my environment before I restarted to work on it.

Answers to your questions.

  • Only the Page folder was opened in the files hierarchy. (Only 18 pages have been created for this project yet.)
  • Only two nodes were opened actively. One of them .razor file the other is razor.cs.
  • Files and toolbox are actively worked.
  • I ran my project a couple of times but I didn't debug. I stopped each time when I returned the editing.
  • I didn't measure any differences between editing with running and editing without running the project.

Note : I think it's working without lag more than before.

I would say I am seeing the same. It is better, but the longer you work in it the slower it gets. The only recourse is to close RBS and re-start it. It then works well for a couple hours and begins to slow again.

Thank you for the feedback. We will continue investigating the cause of this delay and hopefully manage to reproduce it locally. I will post here if there is any new development.

I think I'm seeing the same issue. I've noticed that as I open pages in the editor the memory usage increases, but when I close pages that memory is not released. I can pretty consistently reproduce this by opening a bunch of pages, stopping and starting the app, then closing all the pages. After this the memory usage has increased considerably. I see the same behavior across any app I open in the editor. This makes sense because when I see performance issues it's usually after I've been making changes across several files in the app. I typically don't have problems when I'm only working on one file even if the editor is open for a while.

Hi @GallusRoboticus,

It sounds as if you have found a way to consistently reproduce the problem. Can you send us some of those applications to info@radzen.com with some instructions how to replicate the problem? For example - open those pages, do that, run, close and see a delay when doing that.

We just released a new version 1.16.2 which includes a fix of a memory leak in the code completion, analytics and hint code. Please let me know if it improves the behavior.

1 Like