Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

plugin_host error in build 3101 / 3102 / 3103 ! #47

Open
PixelT opened this issue Feb 9, 2016 · 27 comments
Open

plugin_host error in build 3101 / 3102 / 3103 ! #47

PixelT opened this issue Feb 9, 2016 · 27 comments

Comments

@PixelT
Copy link

PixelT commented Feb 9, 2016

In build 3101 / 3102 / 3103 when using this plugin in random(?) time show error:

plugin_host has exited unexpectedly, plugin functionality won't be 
available until Sublime Text has been restarted

Log from console:

PARSING FILE path\to\file.css
PARSING FILE path\to\file.css
error: plugin_host has exited unexpectedly, plugin functionality won't be available until Sublime Text has been restarted

:(

@gobijan
Copy link

gobijan commented Feb 10, 2016

Came here to post the same thing... For now I use the CSS3 package as a workaround.

EDIT: Hardware is: OS X 10.11.3 + Sublime Dev 3102.

@dafonso
Copy link

dafonso commented Feb 12, 2016

@gobijan, does CSS3 package provide css completion for external files? I was unable to understand how...

As for CSS-Extended, I'm having the exact same problem since I upgraded ST to the new release 3103.

@PixelT
Copy link
Author

PixelT commented Feb 13, 2016

@subhaze did you plan to fix it? :)

@rnnyrk
Copy link

rnnyrk commented Feb 13, 2016

Same issue here. Too bad, the completion example are exactly what I need!

@subhaze
Copy link
Owner

subhaze commented Feb 13, 2016

I'll look into this, there's work in progress on fixing/changing scopes on latest builds of ST 3 which this plugin may use. I've just not had time to dig in yet, but on radar.

@zhaoxin34
Copy link

I like this plugin so much, but it unusable after 3103.

@subhaze
Copy link
Owner

subhaze commented Feb 29, 2016

I plan on updating it, just waiting for all the changes that are happening with scopes to settle down. JS seems to be the hot one at the moment, but just holding off for just a bit longer to see if anything else drastic happens.

@roberthpereira
Copy link

Same issue here :'(

@alexpusch
Copy link

👍
Made sublime practically unusable, and was pain in the ass to figure out why

@subhaze
Copy link
Owner

subhaze commented Mar 4, 2016

is everyone on this thread using the /dev build or /beta ?

@alexpusch
Copy link

I use the latest 3103 build

@subhaze
Copy link
Owner

subhaze commented Mar 4, 2016

OK, that's the latest beta build, the latest build is at 3107. There's been some significant scope changes from 3103 to 3107, so I'm still holding off till a new beta is out since I believe this effects that build the most.

I've not been getting an error in the latest dev builds, but not to say this issue is resolved. I'm just not experiencing it. I also deleted all the cache and reindexed, which may help some that are on the dev release channel.

@roberthpereira
Copy link

i also use the latest 3103 build

@ATouhou
Copy link

ATouhou commented Mar 7, 2016

Same bug for me, this plugin just suddenly started crashing the plugin_host.
Windows 10, Sublime Build 3103

@thiagobraga
Copy link

Same problem here. Debian 7.9, Sublime Build 3103.

@PixelT
Copy link
Author

PixelT commented Mar 14, 2016

I noticed, the error displays only(?) when I used gulp to compile sass / scss files.
When I write simple html / css code (without any gulp or sass / scss) the error doesn't show
Someone else has the same observations?

Edit
I have this error always, when try to compile scss / sass files to css (no matter which way - I try Sass Build + SublimeOnSaveBuild instead of using gulp -> this same effects....)

@PixelT
Copy link
Author

PixelT commented Mar 18, 2016

Testing on 3109 - problem still exist :)

@subhaze
Copy link
Owner

subhaze commented Mar 18, 2016

I'll try to dig into this more, though I'm not having the plug_host crash with SCSS.

Also, pull requests are welcomed.

@kenzouno1
Copy link

Same problem here. Sublime Build 3103.I use SublimeSaveOnBuild to compile.

@PixelT
Copy link
Author

PixelT commented Apr 10, 2016

I change settings from:
"css_extension": [".css",".less",".scss"]
to:
"css_extension": [".scss"],

and seems to work okay.... (30 min short testing)
Tomorrow I will test this longer

@PixelT
Copy link
Author

PixelT commented Apr 10, 2016

Unfortunatelly, this is not help...
When I try add SCSS files to cache, the error will show :(

@subhaze
Copy link
Owner

subhaze commented Apr 11, 2016

Thanks for the feedback. I'm not having crashes as others report and unfortunately haven't had time to work through to try and make something reproducible on my side. I'm running OS X + dev build 3109.

@kenzouno1
Copy link

Testing on 3111 - problem still exist .Using with css cache.

@PixelT
Copy link
Author

PixelT commented May 11, 2016

Testing on 3112 - stil exist :(

@rickdoesburg
Copy link

Still crashing on build 3114

@Alan-flat5
Copy link

I'm also crashing on build 3114. Do you think it's conflicting with another plugin? I hope you can fix this soon, because it would be a very useful plugin!

@YaKazama
Copy link

I also have the same problem, but it is caused by the plugin: Color Highlighter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests