Intel XDK IDE and debug issues

[Brandt__Lars]

I would like to know if I'm the only one with issues, or if others (like me until now) has just put up with the XDK quirks:

Intel XDK: More than often the program will not shut down properly. It seems like it's closing normal, but when you look in tasklist, there are about 4 nw.exe's. XDK will not start again until you force them to close (usually the other exe's will follow if you force the one using the most memory to close). It also seems like there's a memory leak, sometimes consuming up to 2 GB.

Debug: The integrated debugger only seems to work right after XDK has started. The slightest change in code, and the debugger begins to struggle, freezing for a long time. It is then no longer possible to set a breakpoint. It is faster to restart the XDK (even though you have to manually kill the nw.exe processes) and then re-open the debugger.
Also, I wish one would be able to debug initialization (e.g. onload) like you could with the original AppMobi.

These issues are begging to be a pain in the a*s and I was wondering if I'm alone in experiencing this, or if it is something that the engineers are aware of and working on to find a solution.

Intel XDK 2893 (although the issues started a long time ago)
Windows 7 Enterprise, SP1

[Brandt__Lars]

I take it that I'm alone with this one, and engineers are not working on a solution :-(

[PaulF_IntelCorp]

I'm assuming you are referring to these problems appearing when you are using the Emulate tab? Yes, others have described the same issue, and we have been unable to isolate the reason for it. The majority of users to not experience this problem.

Have you tried using the Debug tab as an alternative?

[Brandt__Lars]

Thanks for the tip :-)

The Intel Android Device was not in the list among driver software to choose when updating driver software for my Android device under Other Devices. The UniversalAdbDriverSetup installed with success and I even rebooted my PC.
Instead I got it working by installing Koush’s Universal ADB Driver.

It only works for two of my three main apps though. I'm getting an "Could not generate debug module" error, but no apparent errors in the list:

I noticed that when installing debug module for the project, the ones that work had "CROSSWALK VERSION 15" in the title, while the one not working displayed "CROSSWALK VERSION 11"

Any ideas as to why this project fails?

Thanks!

[PaulF_IntelCorp]

I recommend, first, changing the CW version to 15 in the problem project. Also, the way our debug modules are built, right now, results in incompatibilities with some cordova plugins. That build process is based on an old Crosswalk build process. We are upgrading that for the next major release.

[Brandt__Lars]

I think you guys were working on it while I was testing this morning:-)

I was down to having the project being exactly the same as the working project, even the versions of the plugins, and still it wouldn't work. Then suddenly there was a "Download log file" option in the Debug module error window, but couldn't really pinpoint a particular error in that log. Then I tried again shortly after and voila, it worked.

[Brandt__Lars]

Damn, I spoke too soon. After adding the third party plugin "ImagePicker" I'm back to square one. And this time "Download log file" option is no longer there.

[PaulF_IntelCorp]

I recall seeing some issues with that plugin before, somewhere else. If you check the github repo you'll see that it hasn't been maintained for a while, and that there are a BUNCH of forks, probably due to the lack of maintenance. I recommend trying the Telerick fork, theirs are pretty reliable (https://github.com/Telerik-Verified-Plugins/ImagePicker). There may be other good fork candidates out there, here's a view to all of them > https://github.com/Telerik-Verified-Plugins/ImagePicker/network

[Brandt__Lars]

Thanks, but they all fail, and no log files to give a clue about why.