wbond / package_control

The Sublime Text package manager
https://packagecontrol.io
4.8k stars 814 forks source link

ST2 not responding #558

Closed ahmedelgabri closed 9 years ago

ahmedelgabri commented 11 years ago

After updating Package Control ST2 I see beach ball & it becomes unresponsive & I had to force quit it.

When I open it afterwards ST2 is all missed up, after checking the settings I found that all my packages was under "ignored_packages". After fixing this, it works fine till the next reboot/cold start.

ST: 2.0.2, build 2221 Mac OSX 10.8.4

maxim commented 11 years ago

Same issue. It happens when I try to update all packages (for some reason most packages suddenly have updates). I can update packages one by one, but it would take ages, and sometimes it would get stuck even on that.

maxim commented 11 years ago

Was just upgrading packages one by one and again sudden beach ball when got to Markdown Preview.

wbond commented 11 years ago

Hmm, can your guys enable the debug setting and post a log?

maxim commented 11 years ago

I wish I could help out, but I actually got impatient and upgraded all packages one by one, which means I don't really have an easy way to reproduce this now. @ahmedelgabri perhaps you can try?

ahmedelgabri commented 11 years ago

For some odd reason my post from yesterday wasn't published.

I actually did the same as @maxim, but I'm facing the same problem again on my work machine. I tried to get the debug info & post it here but the problem is that ST becomes unresponsive & I can't even copy the debug info. I have to force quit.

It even affects the whole system & makes it a bit laggy I'm on a very powerful machine, latest iMac 16GB RAM with fusion drive

maxim commented 11 years ago

That gave me an idea. I just looked through my Console.app, and see some Sublime Text 2 "hang reports" that fall on the time when I think this was happening the other day. Here's the relevant piece of trace for sublime process: https://gist.github.com/maxim/c09531e66f08406f0b7b

maxim commented 11 years ago

Here's another one, much crazier. I guess this is what happens when you let it run for a while and it creates too many threads and loops: https://gist.github.com/maxim/4955543d3d5a04e34e35

ahmedelgabri commented 11 years ago

Here is a screenshot for an error popup window in ST2 & ST3 too trying to "upgrade/override all packages" screen shot 2013-08-11 at 10 45 12 am

Even if I removed the ignored_packages setting it doesn't make any difference.

darsain commented 11 years ago

Same issue. Decided to do a clean install of ST2 and slowly restore into pre-crash state, but now some packages can't even be installed. Attempts to install packages like SublimeLinter, StringEncode, and several others are all reporting:

HTTP error 503 downloading https:/nodeload.github.com/username/package/zip/vX.X.X

Screenshot

https://status.github.com/ is reporting All systems operational.

I'm developing a twitch when opening ST2. I'm afraid of next crash. The hell is happening?

FichteFoll commented 11 years ago

I'm also getting this for SublimeCodeIntel:

Package Control: Error downloading package. HTTP error 503 downloading https://nodeload.github.com/SublimeCodeIntel/SublimeCodeIntel/zip/v2.0.1

However, that url also doesn't work when entering it in the browser; you have to replace nodeload with codeload. This leads to the assumption that SCI didn't update their package.json and there is a bug in the PC download code that fails to correct that URL (or it isn't implemented for that case at all).

certainlyakey commented 11 years ago

Several more symptoms: I had several packages after this added to ignored_packages, including SFTP and a couple of code themes. Also Soda visual scheme stopped working after this (but is OK after a reboot).

sveggiani commented 11 years ago

Same problem here. A lot of my packages are now in the ignored_packages section of User Settings file. UI broken and key shorcuts unresponsive after updating to Package Control 2. Restored a copy of my Packages folder solved it. But after a new restart the problem happened again. Is there a way to prevent automatic packages update?

FichteFoll commented 11 years ago

See also #564.

StarZ3r0 commented 11 years ago

Same issue. A lot of my packages are now in the ignored_packages and crash ST2 when I restart.

WilliamVercken commented 11 years ago

Same issue for me. I had to enable them back.

wbond commented 11 years ago

I can't reproduce the issue - can someone provide me with their Package Control.sublime-settings file? That will contain a list of the installed packages and any other settings, such as custom SSL certs.

chipotle commented 11 years ago

Here's my sublime-settings file --

https://gist.github.com/chipotle/9b8326490eea427131a3

wbond commented 11 years ago

@chipotle That seems to be the default one, can your post the User version?

FichteFoll commented 11 years ago
{
    "auto_upgrade_last_run": null,
    "ignore_vcs_packages": true,
    "installed_packages":
    [
        "AAAPackageDev",
        "Abacus",
        "Alignment",
        "AutoFileName",
        "Bracketeer",
        "BracketHighlighter",
        "BufferScroll",
        "Caret-History",
        "CSSLint",
        "DetectSyntax",
        "DocBlockr",
        "Emmet",
        "EncodingHelper",
        "FindKeyConflicts",
        "Git",
        "GitGutter",
        "Inc-Dec-Value",
        "INI",
        "JsFormat",
        "LESS",
        "LineEndings",
        "Markdown Preview",
        "MarkdownBuild",
        "Missing Palette Commands",
        "MoonScript",
        "Package Control",
        "PersistentRegexHighlight",
        "Prefixr",
        "Sass",
        "Schemr",
        "SideBarEnhancements",
        "Sublime Files",
        "sublime-github",
        "SublimeCodeIntel",
        "SublimeLinter",
        "SublimeREPL",
        "Theme - Nil",
        "Theme - Soda",
        "WakaTime",
        "Wrap Plus"
    ]
} 

On ST2.

sveggiani commented 11 years ago

Here's mine on ST 2.0.2, Windows 8:

{ "auto_upgrade": false, "auto_upgrade_last_run": null, "installed_packages": [ "Alignment", "BracketHighlighter", "CanISwitchToSublimeText3", "ChangeQuotes", "Ciapre Color Scheme", "Clay Schubiner Color Schemes", "CSS Color Converter", "CSS Media Query Snippets", "CSSTidy", "DataConverter", "Dayle Rees Color Schemes", "DocBlockr", "Doctypes", "EditorConfig", "Emmet", "FavoriteFiles", "FindKeyConflicts", "Git", "GitGutter", "Goto-CSS-Declaration", "GotoOpenFile", "Help", "HTML5", "HtmlTidy", "Http Requester", "JavaScript Patterns", "JsMinifier", "KeymapManager", "Laravel Blade Highlighter", "LESS", "List LESS Variables", "Markdown Preview", "Monokai Extended", "Nettuts+ Fetch", "Open Folder", "Origami", "Package Control", "Placeholders", "Prefixr", "ReadmePlease", "SFTP", "SideBarEnhancements", "SideBarGit", "StringEncode", "sublime-csspecific", "SublimeCakePHP", "SublimeLinter", "SublimeTODO", "Surround", "Terminal", "Theme - Flatland", "Theme - Soda", "TrailingSpaces", "Ublime Color Schemes", "URLEncode", "WebExPert - ColorScheme" ], "repositories": [ "https://github.com/openam/SublimeCakePHP" ] }

majman commented 11 years ago

Same issue here

chipotle commented 11 years ago

Oops. Ahem. I updated the gist to show the user preferences instead.

https://gist.github.com/chipotle/9b8326490eea427131a3

ahmedelgabri commented 11 years ago
{
    "auto_upgrade_last_run": null,
    "debug": true,
    "git_binary": "/usr/local/bin/git",
    "ignore_vcs_packages": false,
    "installed_packages":
    [
        "Alignment",
        "ApacheConf.tmLanguage",
        "ApplySyntax",
        "AutoFileName",
        "Bower",
        "BracketHighlighter",
        "CoffeeScript",
        "Color Highlighter",
        "ColorPick",
        "DocBlockr",
        "Dotfiles Syntax Highlighting",
        "EJS",
        "Emmet",
        "ERB Snippets",
        "Gist",
        "Git Config",
        "Haml",
        "Handlebars",
        "HTML-CSS-JS Prettify",
        "Jade",
        "jQuery",
        "JS2Coffee",
        "JsFormat",
        "JSON to CSV Converter",
        "LESS",
        "Levels",
        "Liquid",
        "LiveStyle",
        "MaxPane",
        "Origami",
        "Package Control",
        "PHP-Twig",
        "ruby-slim.tmbundle",
        "SideBarEnhancements",
        "Stylus",
        "SublimeLinter",
        "SublimeTODO",
        "Syntax Highlighting for Sass",
        "Tag",
        "TernJS",
        "Theme - Flatland",
        "Theme - Soda",
        "TrailingSpaces",
        "Worksheet"
    ],
    "repositories":
    [
        "https://github.com/Anomareh/PHP-Twig.tmbundle"
    ]
}
wbond commented 11 years ago

I've determined this is an issue only for users with many packages. :-) There is a recursive bug where a list is being extended by itself on each package install operation, which eventually leads to exhausting available memory.

wbond commented 11 years ago

Please take the time to either use Add Repository and add https://sublime.wbond.net/prerelease/packages.json or manually download https://sublime.wbond.net/prerelease/Package%20Control.sublime-package and put it in your Installed Packages/ folder.

This version, 2.0.1-beta1, should fix this bug.

FichteFoll commented 11 years ago

I've since reduced my amount of packages (actually just after posting the list here because the size of the list actually surprised me) by removing those I never really use. Furthermore, I haven't been able to recreate this issue once (since I rarely get to update this many packages) so I guess installing won't help much.

wbond commented 11 years ago

Well, anyone who can help test 2.0.1-beta1, before I push it out to the everyone else, is much appreciated!

mbi commented 11 years ago

I also had this issue. Testing 2.0.1-beta1 now and I could "Upgrade/Overwrite all packages", my packages didn't land in ignored_packages and no beachball either. @wbond anything specific you would like me to test?

ahmedelgabri commented 11 years ago

Same here as @mbi tested 2.0.1-beta1 & it's working with no problems now.

Edit: after restarting sublime & trying to upgrade again I got these. screen shot 2013-08-15 at 11 45 54 am

FichteFoll commented 11 years ago

Had to think for a while why the package wasn't updated until I remembered the "install_prereleases": false setting. Anyway, seems like that's working. No problems so far.

designbyadrian commented 11 years ago

I assume you have to delete the array of ignored packages from the user preferences after upgrading to Package Control beta? (I did, and that worked)

I did have some problems upgrading two packages, and I assume it was because of broken folder permissions (Mac OS). Wouldn't hurt repairing permissions with your Disk Utility, or re-applying correct permissions to that package.

mcbsys commented 11 years ago

Not sure how, but my tiny collection of four packages were all ignored under ST2 on Ubuntu 12.04. Emptying the ignored_packages list fixed it. Seemed to happen out of the blue last week after a couple years of use. Sometimes I forget to close Sublime and Ctrl-C kill it from the console where I started it--maybe that prevented some kind of reset? Ignored were Vintage, RubyTest, SCSS, and SublimeERB.

It took me a long time to find the ignored_packages setting under Preferences > Settings - User. I kept looking at Preferences > Package Settings > Package Control > Settings - User, where my list of installed_packages looked fine. Is there some reason not to list ignored_packages in the same file as installed_packages?

If packages sometimes get added to the ignore list without the user's knowledge, it would be nice if there was a prompt when starting Sublime, "Do you still want to ignore these packages? " Or maybe keep a separate list of temporarily-ignored "installing packages" that gets cleared on restart.

wbond commented 9 years ago

This issue has been fixed in master, and code has been added to prevent the ignored packages issue from happening again due to any other possible bug.

Now, Package Control tracks what packages it has disabled for upgrades and will re-enable them when Sublime Text starts if PC was not able to complete the install process.