EvothingsWorkbench.exe unknow software exception

[maluedo]

Hi all,
firstly thanks for this great "things"

I've buyed one sensortag from TI and I would try your demo, but I can't run the workbench I get an
error trying to start it.

I'm on XP 32 bit.

Thanks for your support

[micke]

Hi, would it be possible for you to post the detailed error message?

Are you using the 32-bit version of Evothings Studio download?

If you download nw.js does it run? (was formerly called node-webkit, Evothings Workbensh runs on nw.js).

Download 32-bit version for Windows here: http://dl.node-webkit.org/v0.11.6/node- ... n-ia32.zip

Best, Mikael

[maluedo]

Hi Mikael,
thanks for your support.

I'm on XP 32bit, node-webkit work fine, instead when I try to run Evo I got this error:

[micke]

Thanks for testing and sending the screenshot. Cannot make anything out of the error message, but it is interesting that node-webkit works.

Now I wonder if you can test to copy the files in the node-webkit download to the Evothings folder? (Replacing the existing node-webkit files in the Evothings folder.) Then test to start nw.exe (not EvothingsWorkbench.exe) and see if that works. If successful this will run Evothings Workbench.

I am thinking perhaps there is some problem with the node-webkit files in the Evothings download, and the above is a way to test this.

It might also be that the Workbench code does something that causes node-webkit to crash

Also I wonder, did the Workbench crash first time you tried it, or did it work initially?

Best, Mikael

[maluedo]

Replacing the file with node-webkit I get the same error.

Yes, workbench crashed first time I runned it

It's something int the workbench that causes the crash...how I can find it?

[micke]

Here are some things to try. I could help but do not have a 32-bit Windows installation at hand.

The file "package.json" contains some basic application settings.

This is the HTML file that is lauched when node-webkit starts:

Code: Select all

"main": "hyper/ui/hyper-ui.html",

You can change the following setting to "true" to get a toolbar and console log once node-webkit is running, this can be useful for debugging:

Code: Select all

"toolbar": false,

The JavaScript code for the Workbench is in the folder "hyper".

You can start out by making some modifications to file "hyper/ui/hyper-ui.html".

First thing, comment out all the script tags (using HTML comment tags), and test if the application starts:

Code: Select all

<!--
   <script src="hyper-ui.js"></script>
   <script>
....
   </script>
-->
</body>

If that is successful, try to see if the file hyper-ui.js loads by moving the comment tag:

Code: Select all

   <script src="hyper-ui.js"></script>
<!--
   <script>
....
   </script>
-->
</body>

If that works, remove the HTML comment tags and start commenting out code in the script tag using JavaScript comments /* ... */

This is a start, just to see if it is possible to get something to launch without node-webkit crashing.

Very best, Mikael

[maluedo]

The application crash just when I load this

<script src="hyper-ui.js"></script>

[Fredrik]

Running "EvothingsWorkbench.exe --enable-logging --v=1" will produce a log file called "debug.log". It should help to find the cause of errors like this.

I've reproduced some sort of crash on 32-bit Windows xp. Continuing to investigate... got these lines; don't seem very useful:

Code: Select all

[556:0206/180954:WARNING:raw_channel.cc(215)] Shutting down RawChannel with write buffer nonempty
[556:0206/180954:VERBOSE1:nw_package.cc(230)] Package startup URL: file:///C:/Programs/EvothingsStudio_Win_32_1.1.0/hyper/ui/hyper-ui.html
[556:0206/180954:FATAL:render_process_host_impl.cc(479)] Check failed: !g_exited_main_message_loop.


I expect there's some uncaught JavaScript exception, but I can't see it in this log.

[Fredrik]

Found the problem: os.networkInterfaces() crashes NW on XP.

I don't see any easy way to fix this. Micke, do you think the server could work without knowing its own address?

maluedo, you should upgrade to Windows 7, 8, or GNU/Linux. Windows XP is no longer supported by Microsoft, which means that while we can do our best to make our software run on it, that may not always be possible.

[micke]

Thanks a lot Fredrik!

I will look into a fix for the problem.