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

Sequel Pro Crashes on Mojave on 1.1.2 - Update 3116 Thread #3516

Keydex opened this issue Aug 6, 2019 · 2 comments


Copy link

commented Aug 6, 2019

For application crashes on macOS 10.14 (Mojave) please see issue #3116. ->

I looked at issue #3116 , this crash is still happening and I can reproduce it on version 1.1.2. However, you guys closed the discussion of it. I can see that it is tagged waiting release, but it's been two years. Either comment at the very bottom of that chain to just use test builds, or make a note on your site that this release version is unstable for mac mojave.

  • Sequel Pro Version: 1.1.2
  • macOS Version: 10.14.5
  • MySQL Version: 5.6

When you close any tab on sequel pro, the application will crash.

Steps To Reproduce

  1. Open Sequel Pro on a mac with mojave
  2. Open a new tab
  3. Close the tab

Expected Behaviour
The application shouldn't crash if I close the tab.

Additional Context
I have tried disabling night mode on it to see if it fixes anything, it doesn't. And I can reproduce this on 3x macbook pros 2018.

default write com.sequelpro.SequelPro NSRequiresAquaSystemAppearance -bool no


This comment has been minimized.

Copy link

commented Aug 6, 2019

This is fixed in the test builds from two months ago, but you should at least comment on the #3116 cause that's the first google result to use the test build. 97c1b85

But some of us would rather have non-test build released. For example a lot of your users are downloading 1.1.2 on the internet and using it. At least push that fix out as a release or something.

@Keydex Keydex changed the title Sequel Pro Crashes on Mojave on 1.1.2 Sequel Pro Crashes on Mojave on 1.1.2 - Update 3116 Thread Aug 6, 2019


This comment has been minimized.

Copy link

commented Aug 14, 2019

I can also duplicate the same issue after upgrading to Mojave on 1.1.2, I prefer using the non-test build version over the test build, wish they had a fix for this on the non-test build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.