Sudden "nwjs quit unexpectedly" error message...

[Synchromystic]

I've been dabbling in MZ for Mac on and off for about a year now, no type of coding knowledge whatsoever so any replies to this will have to be dumbed down pretty good for me to grasp them... But I was creating a few scenes earlier today, everything was working fine and then I added one more line of dialogue to a scene I was working on, hit the "playtest" button, and it immediately crashed. It threw up an "nwjs" quit unexpectedly error and asked me if I wanted to reopen it, but my response doesn't change what happens next: The play test window continues to try to load for a second, then gives the error message again and closes.

The editor and everything is still working just fine, I was using version 1.4.3 and tried jumping around to other versions - including the newer one - and nothing seems to change. I deleted the event that I had finished making just before the problem first occurred, so that my game's situation is exactly as it was when it was working, but I still can't play test. What the heck happened, and how do I go about addressing this?

 

[Tea++]

Which version of Mac OS are you using?

 

[Synchromystic]

I'm running Mojave 10.14.6 on a maxed-out 2018 Mac Mini... And staying there indefinitely since my other big hobby is music production, and I'm afraid if I upgrade to a newer OS some of my audio plugins might have issues. What's weird is that everything was working fine and absolutely nothing on my system changed at all -- I just added a few more lines of dialogue to a tiny event and all of a sudden this started happening, and now I can't do much of anything at all since I can't play test.

 

[Tea++]

Maybe check to see if you're getting an error in the console using the steps found here:

How to check Mac console

If you find an error having to do with either nw.js or MZ please share it here.

Also, please check your debug log for any errors as well. The debug log can be found by right clicking MZ in your steam library, then choosing "Properties>Local Files>Browse" Once your in your installation folder open the folder nwjs-mac and look to see if you have a debug.log file. If you do, please open it in a text reader (like TextEdit) and check if there are any relevant errors there.

 

[Synchromystic]

I managed to find the nwjs-mac folder but there was no debug.log file in it... As for the Console, that made me aware of a "combat_ifmu_ulist error 14" that keeps repeating endlessly, which might explain why my system has suddenly slowed down a bit at performing certain actions. Had to look a bit harder to spot the relevant nwjs errors, but there were a few:

​

I also tried copying all of my game files and moving them to my old MacBook Pro to see if it would work there, and it did -- albeit with a very lengthy load screen that I've never had to deal with before. I had the Visustella plugin open the Console view in the background automatically and it did mention an error involving Chrome:
I've never fooled with anything related to Chrome before so I don't really know what that means either.

 

[Tea++]

I did a little digging on the error, and while I don't use Mac and am not familiar with the system at all, I may have found a lead. I found a case where it had to do with Steam. I would suggest trying these things out.

First try uninstalling and reinstalling after you clear your cache. Here are the steps for doing that:
Start off by uninstalling RPG Maker

1. Clear your Steam download Cache, to do this use the following steps;
a. Open your steam app
b. Go to the Steam menu in the top menu bar and "Preferences"
c. In the side bar on the left, select "Downloads".
d. Click the "Clear download cache" button to clear your cache.

At this point, reinstall RPG Maker

2. After you've done the first step, try these steps as well,
a. Locate RPG Maker in your steam library and right click, select "Properties"
b. Select the "Local Files" tab
c. Click "Verify Integrity of Application Files"

Please also restart your computer before verifying if this solution worked or not.

If this doesn't solve the issue, you may want to consider reinstalling Steam itself. It's a bit rash, but it's not unheard of for the Steam client itself to have problems with it's installation.

Hopefully one of those two things will solve the problem. I'm going to guess that for some reason or another, not all of the required files are being installed, or one that was installed was corrupted and it isn't being replaced.

 

[Synchromystic]

I'll give that a shot, tho it might take me a while to get around to it...
But thanks a BUNCH for the help!!!

 

[Synchromystic]

Welp, I just did all of that, including uninstalling and re-installing Steam. Still doesn't work.

However... Since I was able to play test with a fresh project on my laptop, I decided to try starting a new one on my desktop, which worked until I began re-installing my plugins, and I noticed that the error happens once I turn on the Visustella Core Engine plugin. I can have absolutely nothing else in the project and it will start up perfect, but as soon as I turn that on I get the njws error.

That still doesn't make sense to me, though: This error did begin not long after I had finally bothered to switch to newer, updated versions of all the Visustella plugins... But I still have the older versions that were working before, and when I go back to them now, they also give me the same error. And somehow it was able to work on my laptop even with all of those plugins turned on.

So apparently something in the Core Engine plugin doesn't agree with something in my Mac mini anymore... That's as far as I got, and now I'm stuck again.

 

[Synchromystic]

Started getting really depressed for a while there, but somehow I got it working!!!

And again, it seemed almost random and out-of-the-blue, because after restarting my computer I began fooling around with the options in the Core Engine plugin and noticed one about repositioning enemies, saying that it NEEDS to be on in MZ 1.3 and beyond... I had never read through any of those, but I turned it on and noticed that the new project would actually start with the Core Engine turned on.

I thought, "well surely that wasn't the cause of the problem," but then I went back into my main project and noticed that doing that would SOMETIMES get it to work -- and sometimes it wouldn't. That made me assume I hadn't really gotten anywhere after all... Yet it seemed like after a few back-and-forths it started to work more and more often than not, until I was finally able to start switching my other plugins on again and... Well, now it SEEMS to be fine again.

It's almost like it had to slowly work the bug out of its system... But it's very likely that your suggestion helped it get it's health back on track, lol.

One other thing: I actually forgot to check the "verify integrity of software files" thing until just now, but when I did it said "All 0 files successfully validated."

 

[Tea++]

Ah yes, plugins can cause all kinds of trouble. I'm glad you got it working!

 

[Synchromystic]

I think I've confirmed that the Core Engine setting I mentioned actually IS the problem:

Visustella just released an update of their Sample Project, and I realized I'd never actually looked at this before so I decided to check it out... But when I tried to play it I got the same error repeatedly... So I went in to the Core Engine's Screen Resolution Settings and found the option that says "For MZ 1.3.0+?" and changed the value to "True" and then it started right up.

They really should do something to make that the default, because I doubt anyone is going to jump into MZ at this point and start off with a version lower than the current one. That's extremely stupid, actually. The sample project also has a couple of broken links and embarrassing typos, but I guess overall it serves its purpose.