Jump to content
Sign in to follow this  
DavidRM

Errors when working on my Node.JS server project

Recommended Posts

At this point, I'm pretty much dead in the water. I cannot work on my Node.JS websocket server project without getting error after error.

I've let the software email in a number of bug reports, but I figured I would post here too.

Launch SMS, load my project, attempt a build (Ctrl+F9), I get this:

EurekaLog 6.1.04

Exception:
-------------------------------------------------------------------------------------------------------------
  2.1 Date          : Wed, 1 Aug 2018 08:53:57 -0500
  2.2 Address       : 004088AA
  2.3 Module Name   : SmartMS.exe - (Smart Mobile Studio ID)
  2.4 Module Version: 3.0.0.12
  2.5 Type          : EAccessViolation
  2.6 Message       : Access violation at address 004088AA in module 'SmartMS.exe'. Read of address 8B184795.
  2.7 ID            : 0894
  2.8 Count         : 1
  2.9 Status        : New
  2.10 Note         : 

 

I need a workaround so I can work around this.

Thanks.

-David

Share this post


Link to post
Share on other sites

I found a workaround: I start SMS, load a different project, close it, then open the project I want to work on.

Though I still get an error when closing SMS after that.

-David

Share this post


Link to post
Share on other sites
22 hours ago, DavidRM said:

Did none of the stacktraces sent as bug reports provide anything useful?

Sorry, no. I can see the stack traces, but I can't solve the mystery with them. So I'd really appreciate it if I could get a zip of the project.

Share this post


Link to post
Share on other sites

Oddly enough, the problem has eased up, even without using the workaround.

My speculation is that at least part of the problem has to do with a lot of open source file tabs and maybe some errors encountered in the background compilation.

-David

Share this post


Link to post
Share on other sites

In all probability "something" in the project causes the background compiler to go bananas and kills the thread.
This has happened in some rare cases when inline JS is used, but i think we have seen 2-3 of these over 8 years, so very rare.
Like Jarto says its impossible to figure out "what" causes this from a stack-trace, that only tells is the entrypoint in the IDE which in all likelyhood is not the culprit.
We really want to find out what this is so we can get rid of the behavior, so if you can share the code that would really help!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×