DotNetToJScript icon indicating copy to clipboard operation
DotNetToJScript copied to clipboard

(0, 1) Microsoft JScript compilation error: Out of memory

Open Meatballs1 opened this issue 7 years ago • 2 comments

With larger target binaries (1200KB) observe the above error.

By removing the line splits on the base64 serialized object it is fine - all that string concatenation is bad for cscripts health.

Meatballs1 avatar Nov 06 '17 15:11 Meatballs1

Well, don't do that then ;-) In all seriousness though the tool wasn't really designed with performance in mind, at one point something of that size might have taken 5+ mins to load. If you need a larger binary you could pull it down from a website (WebClient::DownloadData is your friend here) then call Assembly::Load again. Or embed it gzipped into another binary and ungzip it at runtime. As you can call methods on the deserialized object you could easily create a stub loader which has a function you can pass a URL from the JScript to load a new assembly so that you never have main body of the script.

tyranid avatar Nov 24 '17 09:11 tyranid

with Vbscript i tried to add other more crypt algorithms like AES (for performance test) but it keep showing errors like : Object not a collection in 'For Each i in dec' line.

chaimamel avatar Dec 24 '17 23:12 chaimamel