Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My experience with this kind of problem is that unless you can access the external code before feeding it to the <code>iframe</code> (either as an URL or via the <a href="https://developer.mozilla.org/en-US/docs/HTML/Element/iframe" rel="nofollow">srcdoc</a> attribute), the loop will completely interrupt any JavaScript execution. </p> <p>Whatever kind of timeout functionality you implement, it will not be called due to the iframe code execution consuming 100% resources until the browser reports a crash. </p> <p>Your options are:</p> <ul> <li><strong>Sanitize the code automatically</strong> before adding it to the <code>iframe</code>, which proves impractical since there are infinite ways to loop infinitely, and you will not be able to catch them all. You would have to write a scanner script that could detect infinite loops while not crashing in the course of scanning the code. </li> <li>Use a <strong>sandboxing solution like <a href="http://code.google.com/p/google-caja/" rel="nofollow">Google Caja</a></strong> to sanitize the code. However, this will change the code structurally if not configured heavily.</li> <li>In case of an application that has capabilites of <strong>creating virtual environments</strong> and monitoring them, you could execute the iframe code (let's say on a virtual machine of sorts), check if the process locks up and use that outcome to determine if you can safely set the <code>iframe.src</code> property to your code's URL. This might be the only solution that can guarantee some sort of guarantee that this code will not lock up immediately (however, there are many ways to have race conditions at some later point of execution, so there will not be a sure way to say it will never lock up the browser).</li> </ul> <p><strong>Summary</strong>: Unless you can find a way to test the code extensively before showing it in the <code>iframe</code>, you can not guarantee that the iframe code will not lock up the browser tab.</p>
    singulars
    1. This table or related slice is empty.
    1. POJavascript: possible for parent to kill child iframe if it is stuck in an infinite loop?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USarvidkahl
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJavascript: possible for parent to kill child iframe if it is stuck in an infinite loop?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI think this is the most complete answer, not was I was hoping for obviously but informative
      singulars
      1. PO
      1. USasutherland
    2. COThanks, and I must say that I have walked in your shoes when I was looking for a solution to that problem a while ago. You would assume that this problem has been tackled by someone before, but it seems that many people assume that no infinite loops will ever find their way into the iframe. Now that I think of it, there may even be a mathematical proof to the argument that no software whatsoever will be able to determine with absolute success if a particular piece of code will ever not loop forever. `eval` and its derivatives come to mind.
      singulars
      1. PO
      1. USarvidkahl
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload