Quantcast
Channel: bundletransformer Issue Tracker Rss Feed
Viewing all 698 articles
Browse latest View live

Edited Unassigned: bug with last version [124]

$
0
0
Hello, when install last version of bundle transformer i get error :

> Server Error in '/' Application.
>
> During the output text content of processed asset an unknown error has occurred.
> See more details:
> Exception has been thrown by the target of an invocation.
>
> Description: An unhandled exception occurred during the execution of the current web request. Please > > review the stack trace for more information about the error and where it originated in the code.
>
> Exception Details: System.Web.HttpException: During the output text content of processed asset an unknown error has occurred.
> See more details:
> Exception has been thrown by the target of an invocation.
>
> Source Error:
>
> An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
>
> Stack Trace:
>
>
> [HttpException (0x80004005): During the output text content of processed asset an unknown error has occurred.
> See more details:
> Exception has been thrown by the target of an invocation.]
BundleTransformer.Core.HttpHandlers.AssetHandlerBase.ProcessRequest(HttpContextBase context) +1707
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +508
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +96
>
> Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.118.0

It only works with these packages:
<package id="BundleTransformer.Core" version="1.9.25" targetFramework="net452" />
<package id="BundleTransformer.Less" version="1.9.25" targetFramework="net452" />
<package id="JavaScriptEngineSwitcher.Core" version="1.2.4" targetFramework="net452" />
<package id="JavaScriptEngineSwitcher.V8" version="1.2.0" targetFramework="net452" />

Commented Unassigned: bug with last version [124]

$
0
0
Hello, when install last version of bundle transformer i get error :

> Server Error in '/' Application.
>
> During the output text content of processed asset an unknown error has occurred.
> See more details:
> Exception has been thrown by the target of an invocation.
>
> Description: An unhandled exception occurred during the execution of the current web request. Please > > review the stack trace for more information about the error and where it originated in the code.
>
> Exception Details: System.Web.HttpException: During the output text content of processed asset an unknown error has occurred.
> See more details:
> Exception has been thrown by the target of an invocation.
>
> Source Error:
>
> An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
>
> Stack Trace:
>
>
> [HttpException (0x80004005): During the output text content of processed asset an unknown error has occurred.
> See more details:
> Exception has been thrown by the target of an invocation.]
BundleTransformer.Core.HttpHandlers.AssetHandlerBase.ProcessRequest(HttpContextBase context) +1707
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +508
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +96
>
> Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.118.0

It only works with these packages:
<package id="BundleTransformer.Core" version="1.9.25" targetFramework="net452" />
<package id="BundleTransformer.Less" version="1.9.25" targetFramework="net452" />
<package id="JavaScriptEngineSwitcher.Core" version="1.2.4" targetFramework="net452" />
<package id="JavaScriptEngineSwitcher.V8" version="1.2.0" targetFramework="net452" />
Comments: Hello, Hackfaq! Try to install the [Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/en-us/download/details.aspx?id=40784).

Created Unassigned: Combine js files before Uglifying [125]

$
0
0
Is it possible?

currently it does the Minification/Uglyfying/Packing for every single file.

But the way I have structured my project, I have seperated everything into seperate files (simular to how you would organize c# classes etc.)

so I have 116 files being minified seperatly. and its not done corretly because it doesn't see all the references between the file.


--example could be.

__Game.js__
```
var Game = {
...
}
```

__Game.Objects.js__
```
Game.Objects = {
...
}
```

__Game.Objects.Player.js__
```
Game.Objects.Player = function() {
...
}
```

and so on

Edited Unassigned: Combine js files before Uglifying [125]

$
0
0
Is it possible?

currently it does the Minification/Uglyfying/Packing for every single file.

But the way I have structured my project, I have seperated everything into seperate files (simular to how you would organize c# classes etc.)

so I have 116 files being minified seperatly. and its not done corretly because it doesn't see all the references between the file.


--example could be.

__Game.js__
```
var Game = {
...
}
```

__Game.Objects.js__
```
Game.Objects = {
...
}
```

__Game.Objects.Player.js__
```
Game.Objects.Player = function() {
...
}
```

and so on.

But its actually a really "closed" project. and nothing break if I combined all 116 files in one single file, wrapped everything in an anonymous function and obfuscate it to oblivion. (this is really what i want it to do).

Commented Unassigned: Combine js files before Uglifying [125]

$
0
0
Is it possible?

currently it does the Minification/Uglyfying/Packing for every single file.

But the way I have structured my project, I have seperated everything into seperate files (simular to how you would organize c# classes etc.)

so I have 116 files being minified seperatly. and its not done corretly because it doesn't see all the references between the file.


--example could be.

__Game.js__
```
var Game = {
...
}
```

__Game.Objects.js__
```
Game.Objects = {
...
}
```

__Game.Objects.Player.js__
```
Game.Objects.Player = function() {
...
}
```

and so on.

But its actually a really "closed" project. and nothing break if I combined all 116 files in one single file, wrapped everything in an anonymous function and obfuscate it to oblivion. (this is really what i want it to do).
Comments: Hello, bQvle! > Is it possible? Yes, you need to edit the `Web.config` file: ``` <?xml version="1.0" encoding="utf-8"?> <configuration> … <bundleTransformer xmlns="http://tempuri.org/BundleTransformer.Configuration.xsd"> <core …> … <js … combineFilesBeforeMinification="true"> … </js> … </core> … </bundleTransformer> … </configuration> ``` For styles is also exist the same attribute. To facilitate editing of `Web.config` file install the [BundleTransformer.ConfigurationIntelliSense](https://www.nuget.org/packages/BundleTransformer.ConfigurationIntelliSense/) package.

Edited Unassigned: Combine js files before Uglifying [125]

$
0
0
Is it possible?

currently it does the Minification/Uglyfying/Packing for every single file.

But the way I have structured my project, I have seperated everything into seperate files (simular to how you would organize c# classes etc.)

so I have 116 files being minified seperatly. and its not done corretly because it doesn't see all the references between the file.


--example could be.

__Game.js__
```
var Game = {
...
}
```

__Game.Objects.js__
```
Game.Objects = {
...
}
```

__Game.Objects.Player.js__
```
Game.Objects.Player = function() {
...
}
```

and so on.

But its actually a really "closed" project. and nothing break if I combined all 116 files in one single file, wrapped everything in an anonymous function and obfuscate it to oblivion. (this is really what i want it to do).

Commented Unassigned: Combine js files before Uglifying [125]

$
0
0
Is it possible?

currently it does the Minification/Uglyfying/Packing for every single file.

But the way I have structured my project, I have seperated everything into seperate files (simular to how you would organize c# classes etc.)

so I have 116 files being minified seperatly. and its not done corretly because it doesn't see all the references between the file.


--example could be.

__Game.js__
```
var Game = {
...
}
```

__Game.Objects.js__
```
Game.Objects = {
...
}
```

__Game.Objects.Player.js__
```
Game.Objects.Player = function() {
...
}
```

and so on.

But its actually a really "closed" project. and nothing break if I combined all 116 files in one single file, wrapped everything in an anonymous function and obfuscate it to oblivion. (this is really what i want it to do).
Comments: Thanks alot, I overlooked that in the documentation! However i still think it looks more minified then obsfucated. example, > Game.Scene.Renderer will become > e.Scene.Renderer so its still not nonsence to look at. (I am using UglifyJS). Can we make it more unreadable? so that all "pretty names" is packed away and reffered instead?

Commented Unassigned: Combine js files before Uglifying [125]

$
0
0
Is it possible?

currently it does the Minification/Uglyfying/Packing for every single file.

But the way I have structured my project, I have seperated everything into seperate files (simular to how you would organize c# classes etc.)

so I have 116 files being minified seperatly. and its not done corretly because it doesn't see all the references between the file.


--example could be.

__Game.js__
```
var Game = {
...
}
```

__Game.Objects.js__
```
Game.Objects = {
...
}
```

__Game.Objects.Player.js__
```
Game.Objects.Player = function() {
...
}
```

and so on.

But its actually a really "closed" project. and nothing break if I combined all 116 files in one single file, wrapped everything in an anonymous function and obfuscate it to oblivion. (this is really what i want it to do).
Comments: I really like the output of "Packer", but i just get way to many errors because it dosn't handle the multiline syntax very vell. Everything needs ; (that i can live with) but things like ``` if (condition) .... else .... ``` (without brackets) also breaks it.

Edited Unassigned: bug with last version [124]

$
0
0
Hello, when install last version of bundle transformer i get error :

> Server Error in '/' Application.
>
> During the output text content of processed asset an unknown error has occurred.
> See more details:
> Exception has been thrown by the target of an invocation.
>
> Description: An unhandled exception occurred during the execution of the current web request. Please > > review the stack trace for more information about the error and where it originated in the code.
>
> Exception Details: System.Web.HttpException: During the output text content of processed asset an unknown error has occurred.
> See more details:
> Exception has been thrown by the target of an invocation.
>
> Source Error:
>
> An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
>
> Stack Trace:
>
>
> [HttpException (0x80004005): During the output text content of processed asset an unknown error has occurred.
> See more details:
> Exception has been thrown by the target of an invocation.]
BundleTransformer.Core.HttpHandlers.AssetHandlerBase.ProcessRequest(HttpContextBase context) +1707
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +508
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +96
>
> Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.118.0

It only works with these packages:
<package id="BundleTransformer.Core" version="1.9.25" targetFramework="net452" />
<package id="BundleTransformer.Less" version="1.9.25" targetFramework="net452" />
<package id="JavaScriptEngineSwitcher.Core" version="1.2.4" targetFramework="net452" />
<package id="JavaScriptEngineSwitcher.V8" version="1.2.0" targetFramework="net452" />

Commented Unassigned: Combine js files before Uglifying [125]

$
0
0
Is it possible?

currently it does the Minification/Uglyfying/Packing for every single file.

But the way I have structured my project, I have seperated everything into seperate files (simular to how you would organize c# classes etc.)

so I have 116 files being minified seperatly. and its not done corretly because it doesn't see all the references between the file.


--example could be.

__Game.js__
```
var Game = {
...
}
```

__Game.Objects.js__
```
Game.Objects = {
...
}
```

__Game.Objects.Player.js__
```
Game.Objects.Player = function() {
...
}
```

and so on.

But its actually a really "closed" project. and nothing break if I combined all 116 files in one single file, wrapped everything in an anonymous function and obfuscate it to oblivion. (this is really what i want it to do).
Comments: Hello, bQvle! > However i still think it looks more minified then obsfucated. All minifiers of the Bundle Transformer will not give to you a full obfuscation. For these purposes need real obfuscators (e.g. [Javascript Obfuscator](http://www.javascriptobfuscator.com/) or [JScrambler](https://jscrambler.com/)). In most cases, obfuscation by using minifiers is shrinking of names of local variables. As I understand it, you've read the [“Hack proof your Javascript using javascript Obfuscation in ASP.NET applications”](http://www.codeproject.com/Articles/863295/Hack-proof-your-Javascript-using-javascript-Obfusc) article, and therefore believe, that the BundleTransformer.UglifyJs is an obfuscator. I have to say, that while I don't plan to implement in the BundleTransformer.UglifyJs support of `mangleProperties` options. A year ago, I spent a lot of time to implementation of externs support (very similar functionality) in the BundleTransformer.Closure module, but this opportunity is practically not used. Now I have no free time, and other open source projects have higher priority. > I really like the output of "Packer", but i just get way to many errors because it dosn't handle the multiline syntax very vell. Packer is a very old minifier, which has problems with modern JS code. Base62 encoding is not obfuscation, but compression (a kind of replacement of GZip or Deflate). Compressed thus code is easily decoded through the [JavaScript beautifier](http://jsbeautifier.org/). > so I have 116 files... It seems to me, that to process this amount of files is better to use [Grunt](http://gruntjs.com/) or [Gulp](http://gulpjs.com/). I collected useful materials in [“Additional reading and resources”](https://bundletransformer.codeplex.com/wikipage?title=Additional%20reading%20and%20resources#GruntAndGulp_Section) section of documentation, that will facilitate switch to Grunt or Gulp.

Commented Unassigned: Combine js files before Uglifying [125]

$
0
0
Is it possible?

currently it does the Minification/Uglyfying/Packing for every single file.

But the way I have structured my project, I have seperated everything into seperate files (simular to how you would organize c# classes etc.)

so I have 116 files being minified seperatly. and its not done corretly because it doesn't see all the references between the file.


--example could be.

__Game.js__
```
var Game = {
...
}
```

__Game.Objects.js__
```
Game.Objects = {
...
}
```

__Game.Objects.Player.js__
```
Game.Objects.Player = function() {
...
}
```

and so on.

But its actually a really "closed" project. and nothing break if I combined all 116 files in one single file, wrapped everything in an anonymous function and obfuscate it to oblivion. (this is really what i want it to do).
Comments: Hi Taritsyn, Thank you for replying, that correkt! Yes I noticed that packer was entirely ("decrypted"/unpacked) by the browser, so the source in Chrome was the original. :) In the meantime I've had several tries with Closure in Advanced mode. But even when the game runs without errors theres still alot of stuff that doesn't work because of property renames (that just don't cause errors). So it's a pretty heavy task to manage the Externs, and I'll never be sure that I've fixed everything. so I dropped Closure because of that. The perfect solution would be to actually manually choose what properties / variables to mangle. ofc. it would take some time. but then I would be sure that nothing that isn't supposed to, gets mangled. and I noticed they recently made "sort of" that feature with UglifyJS. where you use a regex to determine what properties to mangle. Ill have a look at Grunt/Gulp. Thank you

Commented Unassigned: When SASS imports fail, IIS crashes [126]

$
0
0
I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.

I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).

Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!

__EDIT:__
I found the application error in my Event Viewer:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: Ah, so that path would be the `~/Areas/Stats/Styles/base.scss`

Commented Unassigned: When SASS imports fail, IIS crashes [126]

$
0
0
I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.

I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).

Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!

__EDIT:__
I found the application error in my Event Viewer:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: I could not reproduce this error. Are you using a custom VirtualPathProvider?

Commented Unassigned: When SASS imports fail, IIS crashes [126]

$
0
0
I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.

I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).

Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!

__EDIT:__
I found the application error in my Event Viewer:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: Hmm, strange. I don't believe we're using a custom VirtualPathProvider. I believe we are on MVC version 4.0.20710.0. Could this affect anything? It does appear, from the Event Log, that the `LibSassHost.Native-64.dll` is where the problem is occurring (unless I am misunderstanding it). Is there more information I could provide that would help identify where the problem is coming from? Also, if I could find the place in the source that does these imports, that might help. Could you point me to that place?

Commented Unassigned: When SASS imports fail, IIS crashes [126]

$
0
0
I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.

I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).

Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!

__EDIT:__
I found the application error in my Event Viewer:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: __Update!__ I have a repro for you. I've attached a small web application. Here is how to repro the situation: 1. Extract the application from the ZIP file 2. Open the Security settings for the newly extracted folder, and add NETWORK SERVICE to the user list, with full permissions: ![Image](http://i.imgur.com/1vio3Sv.jpg) 3. Open and build the solution (note: It will require NuGet packages to be restored) 4. Open IIS and make a new site. 5. Set the physical path for the site to the path of the application. For me, it was C:\Users\jlauer\Desktop\SassCrashRepro\MvcApplication1 Settings should look like this (note: I used port 90, but this is not a required step): ![Image](http://i.imgur.com/nQzonkB.jpg) 6. For the Application Pool, set the .NET framework to __v4.0__, and set the Identity to __NetworkService__ Now, attempt to visit the site at localhost (for me, localhost:90). It should fail as I described. __An interesting note:__ when I browse the site using the Debug button in VS (the one that [looks like this](http://i.imgur.com/YnOxnuh.jpg)), everything works, and I get the correct error page. When I do it using the steps described above, IIS crashes. I am unsure of the reason for this. Perhaps it is related to using NetworkService? If you could take a look at this and let me know, that'd be great! I'm am slightly concerned that the native library is having some issues with handling whatever error is happening, since it appears from the Event Log entry that `LibSassHost.Native-64.dll ` is what the w3wp.exe process is having problems with. Hopefully this is enough information to help figure out what's happening! I am happy to provide any more information that you might need :)

Commented Unassigned: When SASS imports fail, IIS crashes [126]

$
0
0
I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.

I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).

Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!

__EDIT:__
I found the application error in my Event Viewer:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: Hello, Jake! This error occurs only in 64-bit mode. This error was contained somewhere in source code of libSass version 3.3.6, and it seems, that it occurs only in assemblies compiled by the Visual C++. Therefore, to solve this problem, I built a LibSass Host for .Net based on the latest version of the libSass (version of July 4, 2016). I recommend you upgrade the LibSass Host for .Net to version [0.5.2](https://github.com/Taritsyn/LibSassHost/releases/tag/v0.5.2).

Commented Unassigned: When SASS imports fail, IIS crashes [126]

$
0
0
I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.

I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).

Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!

__EDIT:__
I found the application error in my Event Viewer:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: Excellent! Thank you for the update. Out of curiosity, what is it about libSass that can cause IIS to crash like that? Is it possible to handle cases like this in the LibSass Host, to prevent issues like this from happening? I am a little wary of using it in case things like this happen again. Thanks :)

Commented Unassigned: When SASS imports fail, IIS crashes [126]

$
0
0
I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.

I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).

Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!

__EDIT:__
I found the application error in my Event Viewer:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: Unfortunately, I don't know how to prevent such errors, because the default error handler didn't work in this situation.

Edited Issue: When SASS imports fail, IIS crashes [126]

$
0
0
I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.

I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).

Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!

__EDIT:__
I found the application error in my Event Viewer:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e

Commented Issue: When SASS imports fail, IIS crashes [126]

$
0
0
I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.

I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).

Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!

__EDIT:__
I found the application error in my Event Viewer:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: Ahh, understood :) A coworker of mine explained to me that often, issues like this that deal with native code make it impossible to catch such errors, like you said. Thanks for being so prompt and figuring this out! Love your work on this, it is really fantastic.
Viewing all 698 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>