Activities of "michal.cadecky@m2ms.sk"

@enis this is where we get the NullReferenceException.

Menu can be null in MainHeader.cs

    private async Task OnNavBarMouseOverAsync() 
    { 
        if (Menu.NavBarStatus == MenuStatus.OpenOnHover) 
        { 
            if (await UtilsService.HasClassOnTagAsync("body", "lp-closed")) 
            { 
                await UtilsService.AddClassToTagAsync("body", "lp-extended"); 
            } 
        } 
    } 

It is possible that Menu might be null but the question is why this is hapenning. The reason why we have included Lepton Theme projects source code to the main solution is crashing caused by Menu being null during disposal.

        public void Dispose()
        {
            if (Menu is not null)
            {
                Menu.StateChanged -= RefreshMenu;
            }

            NavigationManager.LocationChanged -= OnLocationChanged;
        }

Similary we modified the MainSiderbar. But if Menu is somehow null, it implies that component has not been initialized via OnInitializedAsync - how could be this possible?

Hi, we are not able to reproduce this right now. We are trying to investigate it further but it happens randomly. The only thing we are quite sure with is that it happens after sudden application shudown and followed by application (re)start (happens during new initialization).

The application is hosted in IIS and what seems strage is that even though the Application Pool is set to be always running, the application still somehow went idle/off. I am not sure if this is some kind of Blazor Server behavior or it is caused by application instability (but there is no logs regarding crash in log file nor in event viewer).

What we are able to observe are these strange strings cut-offs. It looks like it always begins with some request been malformed and following redirect to error page (?) fails with repetitive issues to fetch some content files - it is searching with adding character by character to the final url - '_content/Volo.Abp.' etc (seems to always fail for LeptonTheme content files). Sometimes the application is able to locate the resource and recovers from the erroneous state but it takes time and also CPU resources.

There are also some SignalR disconnects in the logs but the issue is affecting all users as the application is not responsive while in this state (but we still need to confirm this when the issue happens again).

We would like to consult with you what we can do more to investigate this further and have more information about the issue. Maybe this sounds familiar to you as you might have already experienced this kind of error before and may have some ideas.

Unfortunately we are not able to provide more information regarding the steps to reproduce right now.

Thank you. I had seen the provided link before I have started this thread. Yes, I understand that this is something already in your backlog with a (probably) low priority. That is why we would like to rise attention to this feature and kindly ask for your support and cooperation.

There are several more questions in the original post so I would also like to ask you, if you could take a look on them as well. Thanks!