Software Archive
Read-only legacy content
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.
17060 Discussions

intel xdk fails freeze on start each time

Roi_D_
New Contributor I
3,928 Views

Hi,

When I run intel xdk it freeze on startup on windows with black screen or sometimes half black screen.
What I do is kill nw.exe process intel xdk pops up a dialog if to upload  log, I usually answer yet.
then intel xdk restarts and give option if to continue normal or safe restart.
if I dont choose safe restart in about 30 seconds then it stuck again and need to kill nw.exe process again.
when i choose safe restart all is good and i can open any of my projects.
I'm using intel xdk 2366 on Windows 7.

Thanks,
Roi


 

 

0 Kudos
37 Replies
Roi_D_
New Contributor I
1,600 Views

here is a screenshot http://prntscr.com/8p49t9

 

0 Kudos
John_H_Intel2
Employee
1,600 Views

When you kill the xdk, do you have any extra nw.exe processes running in taskmgr? If you do, kill them, then try restarting the XDK.

 

0 Kudos
Roi_D_
New Contributor I
1,600 Views

there are multiple nw.exe processes. though after killing the one that shows a memory leak all others gets closed.

 

0 Kudos
Roi_D_
New Contributor I
1,600 Views

currently instead of fighting with killing nw.exe I edit global-settings.xdk and change currentProject to be -1 (invalid).

from 3 tests xdk loads fine and i then select the project i want without problems.

 

any news about a fix ?

0 Kudos
PaulF_IntelCorp
Employee
1,600 Views

No fix because we don't understand the source of the problem. This is the only report I've seen that exhibits the symptoms you are describing. Approximately 80% of our users are running on Windows, which means there is something about your system (probably some other piece of software) that is causing this problem. Until we can identify the source we can't provide any fix.

Have you tried running the XDK on another system? If so, do you see the same symptoms? If you don't have access to another system, try creating a Windows virtual machine and running it inside of that VM to see if you continue to see these issues.

0 Kudos
Roi_D_
New Contributor I
1,600 Views

ok I'll try to get another machine or use a VM.

 

0 Kudos
Roi_D_
New Contributor I
1,600 Views

I haven't tried XDK on another system. I'll try to get one or test on VM as you suggested and see. I'll also do some other tests with current XDK.

 

0 Kudos
Weigang_l_
Beginner
1,600 Views

I think I have the same issue that hanging on inilializing page on startup and finding serveral nw*.exe processes runing.

0 Kudos
Pamela_H_Intel
Moderator
1,600 Views

@Roi - if you have a Windows 8 computer, it's the same as a tablet, you can run a Windows 8 build on it. Just an option for running on another device, in case you didn't know.

0 Kudos
Roi_D_
New Contributor I
1,600 Views

I dont have window 8. I'm not changing my work os because XDK has a bug. 

@Weigang - this is the workaround I use when I want to start XDK.

edit %LOCALAPPDATA%/XDK/global-settings.xdk

find currentProject option and change it to -1 so no project is selected on startup. now run XDK and it will not freeze on startup.

 

0 Kudos
Roi_D_
New Contributor I
1,600 Views

editing %LOCALAPPDATA%/XDK/global-settings.xdk and changing currentProject to -1 works for me each time.

Is it possible for a feature request to set XDK to always start with unselected project? this option will solve the issue as this is what I do manually before each start and its fine like this.

 

0 Kudos
Pamela_H_Intel
Moderator
1,600 Views

Roi - I will check with the team on that. Personally, I also would like to open XDK and select my project after opening.

0 Kudos
Pamela_H_Intel
Moderator
1,600 Views

Roi,

I've brought this issue up with the team - opening XDK empty. The problem is workflow related. Since in my work I change projects extremely frequently it would be faster for me if XDK would open empty. But it is more typical that developers will work on a single project over time. To require them to take one more step to get to their project, over time, is tedious. 

Since we have a good workflow for the majority of developers, and there is the currentProject = -1 work around, the need to change workflow is not recommended at this time.

Pamela

0 Kudos
Roi_D_
New Contributor I
1,600 Views

Thanks but what is the workaround? creating a Windows script wrapper to edit the config file and change to -1 pre run of the XDK?

What about an option in XDK to force it to save -1 for me?

 

0 Kudos
Pamela_H_Intel
Moderator
1,600 Views

Yes. I am considering writing a script to change the config file myself.

I will  ask about the possibility of XDK having a switch. That would be nice. Maybe in settings . . .

0 Kudos
Roi_D_
New Contributor I
1,600 Views

ok Pamela. thanks.

 

here is the script I eventually created to run xdk. seems to work fine for me with multiple runs xdk didn't freeze.

 

#!/bin/sh

CONFIG="$LOCALAPPDATA\XDK\global-settings.xdk"
NW="$LOCALAPPDATA\Intel\XDK\bin\nw.exe"
WRAPPER="$LOCALAPPDATA\Intel\XDK\xdk\xdk-wrapper"

echo $CONFIG
sed -i 's/\("currentProject":\) \([0-9]\+\)/\1 -1/g' $CONFIG

start /B $NW "$WRAPPER"  
exit 0

 

 

 

 

0 Kudos
Pamela_H_Intel
Moderator
1,600 Views

Excellent. I am glad your script works. I will do what I can to get a toggle feature added. Though you are the only one who has reported persistent crashing, maybe others have experienced it and just not reported it.

0 Kudos
Reply