Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-18604] LiveView: Running liveview-server status shows that LiveView servers are running when they are not

GitHub Issuen/a
TypeBug
PriorityMedium
StatusOpen
ResolutionUnresolved
Affected Version/sRelease 3.5.1, Release 8.3.0
Fix Version/sn/a
ComponentsLiveView, Tooling
LabelsengTriage, qe-3.5.1
ReporterEwan Harris
AssigneeUnknown
Created2015-02-23T19:01:34.000+0000
Updated2020-01-07T00:24:40.000+0000

Description

Description

When navigating to the LiveView folder within the Studio plugins and running the command ./liveview-server status all the LiveView servers that have been started since LiveView was installed are listed. However if you run *ps aux | grep node* it will show only one or none LiveView processes running. If you try to kill the servers using ./liveview-server stop then it will attempt to kill the servers and will print out the following for each server.
[LiveView]  Closing file/event server process id: 10716
[LiveView]  Error closing server { [Error: kill ESRCH] code: 'ESRCH', errno: 'ESRCH', syscall: 'kill' }

Steps To Reproduce

1. From Studio build a few projects with LiveView enabled, making sure to terminate them once the app has launched and LiveView has connected 2. Navigate to the LiveView folder at /Applications/Appcelerator_Studio/plugins/com.appcelerator.titanium.liveview.core_1.1.0.1424300841/node_modules/liveview/bin 3. Run ./liveview-server status 4. Run .ps aux | grep node 5. Run ./liveview-server stop

Actual Result

3. Multiple liveview servers will be listed 4. Only one liveview server will be shown as running, as expected 5. LiveView will attempt to kill the servers but it will fail

Expected Result

LiveView should not list inactive servers as active

Attachments

FileDateSize
consoleOutput.txt2015-02-23T19:05:46.000+000010985

Comments

  1. Rene Pot 2016-01-14

    This is still an issue. Just discovered it, but nothing changed in performance of my machine after killing about 40 servers (you would expect cpu/memory usage drop). Got the error too.

JSON Source