Launching map gets stuck at 24% "Launching delegate..." and Eclipse uses 650+ MB RAM

[Cokemonkey11]

It happens to be a new map that has not yet been successfully run by wurst.

I launch it by right clicking the w3x file in eclipse and selecting "run as Wurst".

[Crigges]

My eclipse uses 2GB Ram if it is hungry so be be happy with 700MB

The launch seems to be stucked in a infinity loop. Better show us the console output instead of the progressbar.

[Cokemonkey11]

I cleaned and rebuilt wurst, and deleted the wurst/war3map.j file and rebuilt by saving the map in wurstpack, then tried doing again "run as > wurst":

Wurst console only shows:

building project rise-of-daolmir, please wait ...

And here is the requested wurst settings menu (warcraft 3 directory is correct):

Also, the "save map" compile raises an error report.

[Crigges]

Looks like you are using a old wurstscript version.

[Cokemonkey11]

@Crigges nope, it's the newest clean build from peq/Wurstscript/master

[Crigges]

Start eclipse via the eclipsec.exe and show us the cmd output.

[Cokemonkey11]

When I right click map and select "run as > wurst" I get different errors sometimes, it seems. In this particular example:

And here is the output of eclipsec.exe -

https://gist.github.com/Cokemonkey11/8b9494bd99540559bc4d

Edit:

It seems eclipsec was not configured to run with administrative permissions (while eclipse.exe was configured so) - here's the error when eclipsec is running with administrative permissions:

And here's the output in eclipsec.exe -

https://gist.github.com/Cokemonkey11/3c71ca4424a2eeacfbdd

[Crigges]

JMpq-v2 is used instead of v3. This was fixed a few commits ago. Check the stacktrace on your own: The stacktrace points to: at de.peeeq.eclipsewurstplugin.console.WurstREPL.compileScript(WurstREPL.java:641)

This is the line: https://github.com/peq/WurstScript/blob/master/EclipseWurstPlugin/src/de/peeeq/eclipsewurstplugin/console/WurstREPL.java#L641

So since line 641 is } your eclipse plugin version is outdated.

[Cokemonkey11]

Crigges, thanks a lot for the help so far.

Yes, I did find it strange that there weren't any automatic updates in a while.

And here's my full error log (have never opened this view, afaik):

[Crigges]

Ye i know this problem. It was an issue with one special wurstbuild. Just uninstal the Wurstscript plugin via: Help -> About Eclipse -> Installation Details and reinstall it again.

[Cokemonkey11]

I've just done that, and tried to run it again. Running the map as Wurst fails, and here is the error log:

[Cokemonkey11]

@Crigges I think you mentioned that you figured out the problem with this and it should be patched?

[Crigges]

Those "Could not extract xyz errors" should only occur if the file is missing inside the .mpq. Check the following: -Does the map contain those files? -Try a differernt map, maybe jmpq2 broke something -If this is a jmpq bug i need some way to reproduce it. Can you offer me your code and and map?

Edit: However your eclipse setup seems wrong. On your screen you are using the Java perspective.