[Dragokas]

Hi,

how is memory protection implemented in sm and is mem isolation even exists between plugins when one try to write over allocated memory region?

E.g. when one plugin uses old inc prototype, when newly installed extension API have a new prototype with additional arguments.
Can such plugin damage global memory or memory of other plugins?

Thanks.

[asherkin]

Each plugin has a separate virtual address space and all access is bounds checked by the VM, so language features should not be able to interact with the memory space of other plugins.

SM APIs such as StoreToAddress have access to the entire process memory and could if misused, same with regular old memory safety bugs in any native code.

[Dragokas]

Thank you.

And what about extensions, if plugin uses wrong version of inc-file, can it harm memory in adress space of extension?

Example:

old version:

native bool Foo(const char[] a1);

new version:

native bool Foo(const char[] a1, const char[] a2 = "data");

[asherkin]

Not implicitly, but it is important for the extension to check the argument count and avoid reading off the end.