I'm not even totally convinced this isn't what I'm seeing on my own network. It takes pretty extraordinary evidence to prove that it's not the network's fault when we can prove that packets are being delayed or dropped before reaching the client. We need to remember that 99.9% of the time these issues really are transient network problems that have nothing to do with Moonlight. Moonlight iOS and PC have totally different codebases and I haven't personally seen iOS affected myself. I'm highly suspicious of jumping to conclusions that iOS may be affected. This is consistent with the stutter observed, because we are getting a bunch of data dropped and the rest delayed significantly. In the trace I recorded, I saw recvfrom() take over 150 ms to return a single packet at one point. This confirms the issue is not our fault and lies with the network or OS network stack. The Moonlight receive thread is not being preempted during that time or anything, since it's able to run and call recvfrom() again when the first call times out. So it really appears that recvfrom() is blocking for over 100 ms without receiving a packet. Thread is waiting for event/lock with id 0xa33ba8a859006e9f. _recvfrom ← (6 other frames)Ġ0:05.386.880 The thread was made runnable by a timer expiration (handled by CPU 0's timer interrupt handler). Continued abuse of our services will cause your IP address to be blocked indefinitely.00:05.286.573Ĝalled "recvfrom(fd:45, buf:0x3ab2200, len:1.37 KiB, flags:0x0.) = 0 Bytes" for 100.39 ms, end-of-file was encountered.Ġ0:05.286.583ělocked for 100.30 ms (99.9% of recvfrom's duration) starting at priority 47. Please fill out the CAPTCHA below and then click the button to indicate that you agree to these terms. If you wish to be unblocked, you must agree that you will take immediate steps to rectify this issue. If you do not understand what is causing this behavior, please contact us here. If you promise to stop (by clicking the Agree button below), we'll unblock your connection for now, but we will immediately re-block it if we detect additional bad behavior. Overusing our search engine with a very large number of searches in a very short amount of time.
Running a "scraper" or "downloader" program that either does not identify itself or uses fake headers to elude detection.Using a script or add-on that scans GameFAQs for box and screen images (such as an emulator front-end), while overloading our search engine.There is no official GameFAQs app, and we do not support nor have any contact with the makers of these unofficial apps. Continued use of these apps may cause your IP to be blocked indefinitely. This triggers our anti-spambot measures, which are designed to stop automated systems from flooding the site with traffic. Some unofficial phone apps appear to be using GameFAQs as a back-end, but they do not behave like a real web browser does.Using GameFAQs regularly with these browsers can cause temporary and even permanent IP blocks due to these additional requests. If you are using Maxthon or Brave as a browser, or have installed the Ghostery add-on, you should know that these programs send extra traffic to our servers for every page on the site that you browse.The most common causes of this issue are: Your IP address has been temporarily blocked due to a large number of HTTP requests.
0 kommentar(er)
