Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThis is a bit of an unsatisfying answer, basically an argument from personal incredulity. I think you need to reread the question, and find an actual reason why the approach wouldn't work... Your complaint, if it were valid, would prove that type systems, memory protection, capability based security, and all other protection mechanisms don't work. None of these systems protect against things going wrong that their authors haven't thought of. Tbh, this stuff isn't even new - DBMS have been resource constraining queries since the seventies. There's nothing magic going on here.
      singulars
    2. COYes, there are techniques to minimise the impact between well behaving systems. However to protect against "malicious code" you need a seperate system. For example, I can write a simple program in java which will write data to disk in a way that will bring a system to its knees. even ssh or smtp will think there system is unusuably slow. You can use the security manager to prevent this and many other operations until the malicous code cannot acutally do anything, then it will have no impact. Basically, with malicious code, anything you allow it to do can be used against you.
      singulars
    3. COA simple way to slow a machine is to create objects endlessly and trigger lots of GCs. The threads total memory need not be large but can slow your JVM dramatically. Say you disabled all object creation, (making the code pretty unusable) the malicous code could still call methods like File.length() which creates objects in the JNI call and can generate 400 MB/s of garbage, called often enough. Note: this kind of activity can slow not only the JVM but measurably impact the performance of the whole machine.
      singulars
 

Querying!

 
Guidance

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