- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I first upgraded to 1995, the XDK loaded fine.
I don't know what happened, but now it takes about 2 minutes and 15 seconds to open up. It also loses the index file at times and then I have to close and reopen (which takes another 2 minutes to open up again.)
CTRL+Shift+F search also takes a while to actually produce anything (46 seconds), this I noticed in other versions too. At first when I upgraded that search was super fast, but now, it's quite slow again.
Any tips?
Thanks,
David
- Tags:
- HTML5
- Intel® XDK
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello David,
Are you on Mac? We have identified one issue on Mac which relates to NW, when you keep XDK idle for a while and then pick it up, XDK becomes very sluggish. I'm not sure if that is affecting the launch time for you. I would recommend first force closing XDK through Activity Monitor and then restarting XDK and working on a fresh launch. Also, try to find out through your Activity Monitor if any other process running on your machine is hogging CPU and memory. This NW issue is being addressed and will be fixed in next release.
Swati
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Swati,
No, I'm on PC. NW (or other processes) doesn't seem to be taking up an extraordinary amount of memory.
When I posted the topic, I closed out of XDK, then timed how long it took to load up, then once it loaded, I immediately did a search, so these times weren't from XDK being idle for a while.
Glad there's a fix in the works.
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi David,
The NW issue that's being addressed is on Mac, on PC we haven't seen such issue.
Your issue seems to be different. Can you try un-installing XDK completely and then re-installing?
Thanks,
Swati
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Swati,
So I tried to uninstall XDK, but when I did, it wouldn't let me because it said that XDK was still open, but when I open the task manager to close it out, it closes the uninstall window.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Was able to download the latest version over the old latest version, and it still has a super long load time (at least 2 minutues), and occasionally can't find the index file it was using just seconds before.
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi David,
You said one copy of XDK was still open when you tried to uninstall, please remove all the instances of XDK.
Then first remove this directory completely:
/Users/yourUseName/AppData/Local/Intel/XDK.
And then install the new version. Let me know if it still does not work.
Also, check if you have any other utility app running that conflicts with XDK.
Swati
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was facing this on my Mac, but now on my PC it is also slowing down severely, even after fresh reinstall.
Just for example resizing the left panel on the develop tab is really slow, It also sometimes states the program is unresponsive at times then recovers.
According to the Windows task manager, I have plenty of CPU and memory available also its running on a SSD so it shouldn't be resources related.
I first noticed this slow down on build 1995.
System Specs:
OS: Windows 7 Enterprise
CPU: Intel Core i7 2.5Ghz
RAM: 16GB DDR3
GPU: Nvidia Geforce GTX 750.
Any ideas?
Is there a stack trace/log I can look at to help diagnose the problem?
Thanks!
The XDK is awesome.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There have been a bunch of issues related to slow-down of the node-webkit module addressed in the upcoming release. It's due very soon, so with luck you'll see some of this go away with the next release.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, a variant of the "severe performance hit" is definitely related to node-webkit. I am on Windows 7 with Intel XDK 1995, and I have seen similar symptoms when I try to debug via the Emulate tab that invokes the node-webkit. The nw.exe starts hogging CPU.
-Mark

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page