I have got one weird issue. I am working on an asp .net mvc application. I have a refresh button that build some data and view models in the controller code, and returns the partial view back. Well this refresh does work good the very first time. But when i try to click my refresh button again, a javascript alert comes saying
"out of memory at line 56"
I checked my task manager to see on whats happening. I have a 3GB memory and when this error alert shows up the used memory is 1.41 GB. Its normal usage as it looks like. But I don't know why it shows the javascript error alert.
This problem happens in my local workstation where I am doing development of this application.
Any thoughts or comments to trouble shoot or solve this issue is appreciated. I ma using IE7.
Any infinite loops in there? Javascript doesn't like those.
Another possibility - is there any Flash on the page? Apparently there have been issues related to that in the past where updating your version of Flash fixes the problem.
Related
My website has a lot of menus and submenus in its index page and these submenus are loaded from the db.Ajax is used to load the submenus. So its taking a lot of time to load the full page. How will i reduce the loading time.I am using asp.net mvc3 and sql server 2008 database
It's very hard to tell what could be the bottleneck in your solution without actually seeing it, but it sounds that you can benefit greatly by doing caching, in ASP.NET MVC it's quite easy to do, here is another great tutorial on the subject. Oh and remember -> “There are 2 hard problems in computer science: caching, naming, and off-by-1 errors” ;)
There are many things that could be going wrong and causing your application to run slowly.
I’d recommend you turn the trace feature on because that will tell you what may be wrong. As Dimitar Dimitrov already mentioned you can try to cache the query in some way so you don’t have to retrieve it every time.
Another option would be to optimize the query so that it fetches all menus and submenus in one query.
But again, don’t do anything specifically until you’ve profiled your application to see where specifically is the issue.
my site is ASP.NET,C#, .net 4, using Umbraco 4, IIS 7.5 it has been working great for months but suddenly its taking ages just to load a single page and mostly not loading at all.
The DB looks fine,
I've restarted the site,
recycled the APP pool,
looked in the logs, it just looks like jibberish
Does anyone have any ideas as to how I can investigate further. No I am not asking you to fix my site or tell me why it is not working, I just want to know other methods for investigating the problem so I can get to the bottom of the issue.
IIS LOG:
http://pastebin.com/msjzty7m
Thanks
Use Google Pagespeed Insights to see where the problems might be.
I have a couple of suggestions:
Set up the ELMAH error log and take a look if some unhandled expcetions.
Set up mini profiler, maybe it is a bottle neck inside a new added script.
Use google PageSpeed Insights to analyze your pages.
My first guess would be it is infact a data issue. Not that it's taking a long time to grab the data but to process it. I've had a few times now where a page is around 138Kb but took over 3 seconds to wait for the page before rendering. Basically this was cause it was running a 3 tier repeater (repeater inside repeater inside repeater) to create the menu system. So even though the site wasn't big it was taking time processing this menu before sending it out.
Suggestions from me would be to comment out anything new that you've added before this date and bring stuff back in slowly till you find the problem part. After that you can look at caching. And if it's a module (.ascx) use # Output Caching and that could help.
This is not loading at all... the online tools can not help, you need to investigate whats happens on the server.
The tools for that is the process explorer from sysinternals to see what is running slow your server, then the autoruns to see what you loading with out your knowledge and also slow down your system, and the tcpView to see who is connected to your server.
I'm having some problem finding the source of the problem, but here it goes, maybe you know the magic answer.
I'm running this asp.net site with an AJAX updatePanel on my local machine, and everything works just fine, since it's where I developed it. Now, a few days ago, I uploaded the files to my web-host and assigned every single DataBase, and there is no error messages, even though it's still set to debug mode. There is a problem though, whenever I click an element which triggers my asp.net AJAX updatePanel to update, the whole site is updated(which it should not, only the Panel), and my jQuery's (document).ready is called every time as well.
Thank you for any help, I have no idea why this does not work online, nor' do I know why it does work on my local machine.
I have choosen not to upload the code, since I have no idea where the problem might lie, please feel free to ask for the code and I shall reply :)
Have you checked that your web host either:
a) Is running .net 3.5
b) Has the Ajax extensions for .net 2.0 installed
...and that you are testing locally with the same?
Umbraco version: umbraco v 4.0.0 (Assembly version: 1.0.3327.20280)
Asp.Net: .Net framework 2.0
Windows server 2008 with IIs7
Sometimes when viewing a page with a contained macro, the macro part of that page is completely removed, not rendered, no error no nothing only a incomplete page. Loading the same page again, it's rendered correctly. This occurs very rarely.
When investigating more deeply I found out that this is somehow connected to the recycling of the application pool in which umbraco is running in. Setting the application pool to recycle itself every 1 minute I could reproduce the behavior more often than with the default recycling time but still not consistently after every recycling.
I was never able to reproduce the error when adding the umbDebugShowTrace=true, the page always renders correctly when having it set to true.
Has anyone got a clue about what can cause this or have anyone seen this before?
Note. It just not a particular page with a macro the got this behavior, every page on the site that have a macro on it acts like this when the problem occurs.
I can't replicate your issue - so I suggest you ask this question at our.umbraco.org
There is will get a bit more visibility by the Umbraco core team who may be aware of the issue.
If you have proper steps to reproduce the bug then submit it to the umbraco codeplex site so that it can get fixed.
T
If you don't know what the operation aborted error is, here's a Microsoft KB Article about it, http://support.microsoft.com/default.aspx/kb/927917 . There's also tonnes of posts about it but the simple answer for it's occurrence is this; the error only occurs if you try to manipulate a DOM element via JavaScript before the element you are trying to manipulate is loaded.
I know how Internet Explorer's (IE) infamous Operation Aborted occurs and know how to fix it. The problem I have is a very weird scenario. Testing locally and on a development machine with IE7, I never ever get the operation aborted error (both sites running as http).
However on our client's testing site it occurs all the time. Unfortunately my testing environment is not the same as the client's testing environment, so that adds some variables to the mix, but the main difference I see is that the client's testing site is using SSL.
Has anyone ever had the Operation Aborted error only for an SSL site?
The other thought that popped in my head was that it was a latency issue. Locally the site loads up almost instantaneously whereas on my client's testing site, the page loads slower. So with that in mind, I got Fiddler running and simulated the performance to run at old school modem speeds, still no operation aborted error locally or on our own testing server.
FYI: The site is an ASP.NET 2.0 Site using ASP.NET AJAX Extensions 1.0. The page with the issue also has the AJAX Control Toolkit's Cascading Drop Down on it.
And yes as far as I can tell all JavaScript that manipulates the DOM is at the end of the markup, not the beginning.
Any help or comments is greatly appreciated.
Well after scouring the Internet I found the issue. It has to do with a bug in the the ASP.NET AJAX client-side framework.
I'll paraphrase what I found:
The issue is a race condition that occurs due to an Internet Explorer/ASP.Net AJAX bug. The probability of encountering this issue increases when the application has a significant number of ASP.Net AJAX enabled server controls on the web page. The issue is explained here, http://seejoelprogram.wordpress.com/2008/10/03/fixing-sysapplicationinitialize-again . I have added this fix to the project I'm working on.
This fix is still required if using ASP.NET 3.5 SP1.
I guess the reason why you don't have SSL on your test box is due to the cost of the certificate. Did you know you can get Free short term certificates? I've often used them to sort out issues like this.
For example RapidSSL do a free 30 day certificate.