Titanium JIRA Archive
Appcelerator Community (AC)

[AC-5035] Appcelerator hangs on "Loading Studio"

GitHub Issuen/a
TypeBug
Priorityn/a
StatusClosed
ResolutionFixed
Resolution Date2017-06-19T16:18:28.000+0000
Affected Version/sAppcelerator Studio 4.5.0
Fix Version/sn/a
Componentsn/a
Labelsn/a
ReporterCameron
AssigneeShak Hossain
Created2017-06-17T14:11:08.000+0000
Updated2018-12-04T13:26:00.000+0000

Description

I've never encountered this problem before. I haven't launched studio in about a week. Starting today, when I launch, I successfully get past the "Validating Studio" screen but then at the "Loading Studio" screen everything just hangs. I've force-quit and reloaded many times with the same result. Reboot with same result. I've attached the report that happens when I force quit. Let me know if there is any other data point. Im stuck in the water Help

Attachments

FileDateSize
Report.rtf2017-06-17T14:09:20.000+00001069785

Comments

  1. Cameron 2017-06-17

    Ok I solved the issue by going to "appc login" from the command line, and then launching the app all worked. Seems weird?
  2. Kondal Kolipaka 2017-06-19

    [~hansknoechel]- Thanks, I'll check that.
  3. Kondal Kolipaka 2017-06-19

    A quick workaround is, do logout from the terminal and login again and then launch the studio. To identify the root cause, whenever studio get into this state - ask them to capture the thread dump for the studio which is mentioned here - http://docs.appcelerator.com/platform/latest/#!/guide/Crashes_and_Freezes
  4. Kondal Kolipaka 2017-07-11

    [~johngoodland] - Unfortunately No. We have to go to terminal and do logout and login again. Will work this on priority with your help, could you please share your studio thread dumps while it was stuck on studio spash screen. That would help me to see where is the problem. Please follow the below link to capture thread dumps. http://docs.appcelerator.com/platform/latest/#!/guide/Crashes_and_Freezes *From the above doc:*

    Open a command prompt.

    Type jps -v shows you a list of jvm process ids. You should see one referencing Eclipse.

    Type jstack >> logfile.logto dump the stack trace for the specified VM process id. Copy this into a file and attach it to the JIRA ticket. You may need to pipe the output to a location where you have write permissions, i.e.:

    c:\Program Files\Java\jdk1.6.0_29\bin>jstack 2616 >> "C:\Users\Username\Desktop\test2.log"
  5. Kondal Kolipaka 2017-07-11

    That's right!, only thread dumps are useful in this case. However, will analyze by invalidating the session and see if we can able to reproduce the problem.
  6. Pablo Liz 2017-10-31

    I had the same problem today with Axway Studio 4.10.0.201709271713 force quit, then terminal appc login, restart the app seemed to work.
  7. Christi 2018-12-04

    Not sure why this is closed as fixed, it is still happening in Axway Studio 5.1.1.201809051655.

JSON Source