Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in [Microsoft JScript runtime error]: Out of stack space #46

Open
dizzib opened this issue Feb 29, 2012 · 3 comments
Open

Error in [Microsoft JScript runtime error]: Out of stack space #46

dizzib opened this issue Feb 29, 2012 · 3 comments

Comments

@dizzib
Copy link

dizzib commented Feb 29, 2012

After upgrading from 1.x to 2.x I'm now getting the following error when attempting to retrieve any js file. However Sass/Css is working ok and all 5 Core tests are passing. This happens either when upgrading via Nuget to 2.0 or via Git to 2.1.

I suspect this issue was introduced in v2.x.

Please let me know if you need any more info.

Thanks,
Andy.

[ActiveScriptException: Error in [Microsoft JScript runtime error]:
Out of stack space
at line 8(154022)
Error Code: -2146828260 (0x800A001C)
Error WCode: 0

]
SassAndCoffee.JavaScript.IEJavaScriptRuntime.ThrowError() in P:\DEV.OPENSOURCE\DotNet\SassAndCoffee\SassAndCoffee.JavaScript\IEJavaScriptRuntime.cs:90
SassAndCoffee.JavaScript.IEJavaScriptRuntime.ExecuteFunction(String functionName, Object[] args) in P:\DEV.OPENSOURCE\DotNet\SassAndCoffee\SassAndCoffee.JavaScript\IEJavaScriptRuntime.cs:67
SassAndCoffee.JavaScript.JavaScriptCompilerBase.Compile(String source, Object[] args) in P:\DEV.OPENSOURCE\DotNet\SassAndCoffee\SassAndCoffee.JavaScript\JavaScriptCompilerBase.cs:35
SassAndCoffee.JavaScript.JavaScriptCompilerContentTransformBase.ExecuteWithArguments(ContentTransformState state, Object[] args) in P:\DEV.OPENSOURCE\DotNet\SassAndCoffee\SassAndCoffee.JavaScript\JavaScriptCompilerContentTransformBase.cs:33
SassAndCoffee.JavaScript.CoffeeScript.CoffeeScriptCompilerContentTransform.Execute(ContentTransformState state) in P:\DEV.OPENSOURCE\DotNet\SassAndCoffee\SassAndCoffee.JavaScript\CoffeeScript\CoffeeScriptCompilerContentTransform.cs:45
SassAndCoffee.Core.ContentPipeline.Execute(String physicalPath) in P:\DEV.OPENSOURCE\DotNet\SassAndCoffee\SassAndCoffee.Core\Pipeline\ContentPipeline.cs:63
SassAndCoffee.Core.InvalidatingCache.GetOrAdd(String key, Func`2 generator) in P:\DEV.OPENSOURCE\DotNet\SassAndCoffee\SassAndCoffee.Core\Caching\InvalidatingCache.cs:64
SassAndCoffee.Core.ContentPipeline.ProcessRequest(String physicalPath) in P:\DEV.OPENSOURCE\DotNet\SassAndCoffee\SassAndCoffee.Core\Pipeline\ContentPipeline.cs:50
SassAndCoffee.AspNet.PipelineHandler.ProcessRequest(HttpContext context) in P:\DEV.OPENSOURCE\DotNet\SassAndCoffee\SassAndCoffee.AspNet\PipelineHandler.cs:38
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +625
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +270

@dizzib
Copy link
Author

dizzib commented Feb 29, 2012

Upon further investigation it seems my box doesn't have any IE installed since I removed it a while ago. Since IE9 contains the chakra jscript engine I may try to install it tomorrow and report back. Cheers!

@dizzib
Copy link
Author

dizzib commented Mar 1, 2012

Ok, installing IE9 fixed this issue! Unfortunately I'm now getting problems where changes to files are not being picked up even with caching fully disabled. I'll file this as a new issue and investigate further.
Cheers,
Andy.

@dizzib dizzib closed this as completed Mar 1, 2012
@kogir kogir reopened this Mar 1, 2012
@kogir
Copy link
Contributor

kogir commented Mar 1, 2012

My 2.1 branch is currently closer to a disaster-in-progress than a work-in-progress. I'd be very wary of running it in production (though I do with some success). I want to create a benchmark suite and comprehensive test suite before even thinking of releasing it.

I'll definitely look into the stack overflow on 2.0. You shouldn't have to install IE 9 for things to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants