[TIMOB-19646] Windows: Orphaned MSBuild processes after building a project
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | None |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2015-10-28T14:10:21.000+0000 |
|---|
| Affected Version/s | Release 5.0.1 |
|---|
| Fix Version/s | Release 5.1.0 |
|---|
| Components | Windows |
|---|
| Labels | qe-5.0.3 |
|---|
| Reporter | Ewan Harris |
|---|
| Assignee | Kota Iguchi |
|---|
| Created | 2015-09-30T13:31:16.000+0000 |
|---|
| Updated | 2015-11-06T21:01:14.000+0000 |
|---|
Description
Description
When building a project for Windows Platform after the build has finished there are 3 orphaned MSBuild processes.
Steps to reproduce
1. Build a project using appc run or ti build
2. Check Task Manager
Actual result
There will be 3 orphaned MSBuild processes
Expected result
There should be no orphaned processes after building
Comments
JSON Source
https://github.com/appcelerator/titanium_mobile_windows/pull/456
Verified using: Windows 10 Pro Appc Core: 5.1.0-42 Appc NPM: 4.2.1 Ti SDK: 5.1.0.v20151104190037 When building for Windows Platform there are no longer any MSBuild processes left around when the build process has ended Closing ticket