title: Javascript timer puzzle
body: <p>This is a weird scenario I just experienced and I am not sure how to phrase the question.</p>
  
  <p>It may be best to describe my application and what it does 1st.</p>
  
  <p>I have an IP camera connected to my router.
  I use a C# VLC wrapper to get 10 frames a second using a RTSP protocol.
  I then upload to my web server using a [web method] these seperate jpegs to my server.</p>
  
  <p>Then via browser using a javascript timer set to 100ms it renders the image into a HTML image control by calling an ashx page repteadly.</p>
  
  <p>Now this has worked for a few days OK.</p>
  
  <p>Now this is what I have experienced in the last 48hrs.</p>
  
  <p>The images coming from the IP Camera was jumpy. That is to say sometimes the images flow in a timely order and sometimes it will slow down, stop and speed up again to 'catch up'.</p>
  
  <p>I noticed when viewing via a web browser client on another PC on my network that the javascript  timer calls were slow and sometimes stopped for periods of time. I used Google Chrome to view how often the ashx url was being called.</p>
  
  <p>I closed down my own applications. Rebooted all my PCs and started VLC application without using the wrapper. Again, the flow was 'jumpy'.  So the conclusion there was that it was not my application.</p>
  
  <p>For some reason I decided to log into my router (192.168.0.1).</p>
  
  <p>Page was not found.</p>
  
  <p>In fact I had to do a complete restart of my router to be able to access my router 'page'.</p>
  
  <p>As soon as I did this everything worked OK again.</p>
  
  <p>So, the 2 questions I have is (1) why could I not access my router through that IP address and (2). Why was my javascript timer crashing to a stand-still?</p>
  
  <p>Like I said this is a weird scenario and I would not blame anyone for wanting to close or vote down this question.</p>
  
  <p>But on the off-chance this is a known thing I would like to be educated.</p>
  
  <p>Thanks</p>