Testing locally fails third build onwards with v1.2.173

#1

I get a “Launching Local dmengine failed” error almost every time I try to build locally. It consistently happens every THIRD build, for some reason, and every build thereafter; closing down the build window always allows two fresh builds before failing.

It started happening after updating Defold to 1.2.173.

The project I’m testing is minimal; one collection with a script attached to it and one module.

Update: I’ve now tried the following things to resolve this;

  • Restart Defold
  • Restart wifi
  • Restart the Mac

A video of the issue using an unedited blank project:

Is it time to revert to an earlier version of Defold? :cry:

1 Like

#2

After downgrading I can confirm v1.2.172 doesn’t have this issue.

0 Likes

#3

@JCash could this somehow be related to the socket changes (dmSocket)?

1 Like

#4

It’s of course what first comes to mind. However, I don’t recall any obvious changes that would produce this type of behavior. We’ll have to look into this.

2 Likes

#5

Issue: https://github.com/defold/defold/issues/5215

1 Like

Defold 1.2.173 has been released