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

Text-entry mode crash #2111

Closed
eliasbe opened this issue Oct 2, 2015 · 20 comments
Closed

Text-entry mode crash #2111

eliasbe opened this issue Oct 2, 2015 · 20 comments

Comments

@eliasbe
Copy link

@eliasbe eliasbe commented Oct 2, 2015

After restart I can do 1 web search then every time I tab to the 3rd pane QS crashes

Running El Capitan (started after I updated) and QS version 1.3.1

@eliasbe
Copy link
Author

@eliasbe eliasbe commented Oct 2, 2015

Console says
2.10.2015 13:55:19,933 com.apple.xpc.launchd[1]: (com.blacktree.Quicksilver.59552[597]) Service exited due to signal: Segmentation fault: 11

@molachai
Copy link

@molachai molachai commented Oct 3, 2015

Getting the exact same error. I use a websearch for YubNub (setup detailed here: http://www.lifeclever.com/quicksilver-yubnub-rapid-web-searches-and-more/). Sometimes I don't even get the first search before QS crashes. Has been happening since I went to El Capitan betas. Now running full El Capitan 10.11.

Error from console:
10/3/15 12:43:04.852 com.apple.xpc.launchd[1]: (com.blacktree.Quicksilver.95392[3570]) Service exited due to signal: Segmentation fault: 11

@skurfer
Copy link
Member

@skurfer skurfer commented Oct 3, 2015

I’m not seeing anything like this. Which interface are you using? (If you don’t know, go to Preferences → Appearance)

@molachai
Copy link

@molachai molachai commented Oct 3, 2015

I'm using Primer, but it happens on all of them.

On Sat, Oct 3, 2015 at 1:42 PM, Rob McBroom notifications@github.com
wrote:

I’m not seeing anything like this. Which interface are you using? (If you don’t know, go to Preferences → Appearance)

Reply to this email directly or view it on GitHub:
#2111 (comment)

@eliasbe
Copy link
Author

@eliasbe eliasbe commented Oct 3, 2015

I'm using mini. This same error occurs when I try to rename files and do other opperations that make me tab to the 3rd pane. However some triggers that have the 3rd pane empty in text mode work.

@molachai
Copy link

@molachai molachai commented Oct 4, 2015

Woop. Spoke too soon. Did some testing. The YubNub search I have programmed to a trigger (Command-Shift-Y) crashes on the following interfaces:
Mini
Primer
White Bezel
Window

I've successfully completed multiple searches with no crashes on the following interfaces:

Bezel (built-in)
Bezel Classic
Flashlight
Menu
Mini-Bezel
Nostromo

Same error as the previous:
10/4/15 00:06:49.557 com.apple.xpc.launchd[1]: (com.blacktree.Quicksilver.95392[3866]) Service exited due to signal: Segmentation fault: 11

@skurfer
Copy link
Member

@skurfer skurfer commented Oct 4, 2015

I can reproduce this in the listed problem interfaces. Can’t say that I know where to start fixing it, though.

@eliasbe
Copy link
Author

@eliasbe eliasbe commented Oct 4, 2015

Switched interfaces and it works exept when creating triggers then it
crashes.

On Sunday, October 4, 2015, Rob McBroom notifications@github.com wrote:

I can reproduce this in the listed problem interfaces. Can’t say that I
know where to start fixing it, though.


Reply to this email directly or view it on GitHub
#2111 (comment)
.

@DavidShepherdson
Copy link

@DavidShepherdson DavidShepherdson commented Oct 5, 2015

Sounds similar (in terms of the symptoms) to #2045? Does the workaround of moving the Quicksilver window to a non-retina display work for this issue too?

@molachai
Copy link

@molachai molachai commented Oct 5, 2015

Not sure. My MacBook Pro doesn't have a retina screen, but it is the higher resolution one. Not 1440x900....can't remember the exact dimensions right now.

On Mon, Oct 5, 2015 at 3:46 PM, David Shepherdson
notifications@github.com wrote:

Sounds similar (in terms of the symptoms) to #2045? Does the workaround of moving the Quicksilver window to a non-retina display work for this issue too?

Reply to this email directly or view it on GitHub:
#2111 (comment)

@skurfer
Copy link
Member

@skurfer skurfer commented Oct 6, 2015

Sounds similar (in terms of the symptoms) to #2045?

The crash log looks very similar. Probably the same issue. And the trigger thing makes sense, since the “command builder” is pretty similar to Primer.

@skurfer
Copy link
Member

@skurfer skurfer commented Oct 6, 2015

Having experimented some more, this seems to be caused by the interface switching to text-entry mode in any pane. I can reproduce it just by hitting . in the first pane. So hopefully that will get us closer to an answer.

@samuelholder
Copy link

@samuelholder samuelholder commented Oct 13, 2015

I'm using primer on a retina macbook pro. Crashes.

I use primer on older macbook air (NR). No crash.

@skurfer
Copy link
Member

@skurfer skurfer commented Oct 14, 2015

I’m going to file a bug with Apple and see where that goes.

@skurfer
Copy link
Member

@skurfer skurfer commented Oct 18, 2015

If you comment out the two lines that make the text resizable, the crash goes away, but then you can’t see the text as you type. Fun!

@skurfer skurfer changed the title Web search 3rd pane crash Text-entry mode crash Oct 18, 2015
@plainclothes
Copy link

@plainclothes plainclothes commented Oct 20, 2015

Sooo glad I found this! I've been battling this for months! I wish had remembered this group instead of bugging the Twitter account.

Switched from my beloved Primer to Nostromo and my text editing woes appear to be gone!

@skurfer
Copy link
Member

@skurfer skurfer commented Oct 21, 2015

Apple bug report 23198852.

@n8henrie
Copy link
Member

@n8henrie n8henrie commented Oct 22, 2015

I think I have the same issue, but on my new 11.6" Macbook Air. Instant crash on going to text mode with Primer. Bezel works fine.

Console: 2015-10-21 8:04:13.354 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.oneshot.0x10000012.Quicksilver[1025]) Service exited due to signal: Segmentation fault: 11

Quicksilver 1.3.2 (4014)
OSX 10.11 and 10.11.1

@clnrvell
Copy link

@clnrvell clnrvell commented Nov 2, 2015

Switching from primer interface to bezel seems to fix the crashing issue for now as molachai stated. Will you post here if you receive an update from apple?

@skurfer
Copy link
Member

@skurfer skurfer commented Dec 9, 2015

This was fixed in 1.3.3

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

8 participants