Crash when closing a tab on macOS Mojave #3116
Comments
|
Which version? |
|
Hello! Having same issue with version 1.1.2, build 4541 (602e11a) |
|
I also this using Mojave 10.14 Beta (18A336e) and Sequal Pro 1.1.2 Build 4541 |
|
Pretty sure that it doesn't occurs in the master branch builds. |
|
Not happening on latest Mojave version (not related to any update of Sequel Pro) - so probably bug fixed by Apple. I think we can close this one? @jpike88 |
|
This issue is occurring again on a later Mojave build: 10.14 Beta (18A353d) and Sequel Pro Build 4541. When I close a tab the entire app crashes. Probably best to wait on the next Mojave build and see if it fixes itself again. |
|
This is still happening on Public Beta 5. It's probably Mojave related but since it's one of the few apps having this issue, might be something in the way it handles the closing of tabs. |
|
I'm seeing this with 18A365a and Sequel Pro build 4541 (602e11a). The app crashes whenever I close a connection tab. |
|
Just updated to latest Mojave version ( |
|
I built master with the Xcode beta and it does not have the same issue. |
|
Still happening on Mojave 10.14 Beta (18A384a) |
|
It's crushing my soul. macOS 10.14 Beta (18A384a) |
|
Most likely a duplicate of #2609 |
|
Exactly, the crash occurs on: |
|
I confirm that crash occurs also on public release of macOS 10.14. Steps to reproduce: Open SequelPro |
|
Same issue here |
|
I have the same issue. V 1.1.2 are there any work arounds? |
|
Sadly, the only workaround is to use a different sql client until @abhibeckert starts doing something about it. |
|
Just to add I have same issue, close any tab and it instantly crashes. v1.1.2 Thanks |
|
Same issue: Sequel Pro: 1.1.2 - Build 4541 (602e11a) Here's a crash log (expand to view - to save future readers!)
|
|
It's now clear that everybody has the same issue. If you want to get notified when this is fixed, hit the Subscribe button. |
|
Just so you know, the issue is not happening on the latest nightly; Build 5224 (3477d22) which I just installed through homebrew. |
|
We are working on new nigthly build and release for Mojave with Dark Mode also. Please don’t add more crashreports here, we are aware of this issue. |
But is it safe? |
|
@lwiml Yes, I did this assembly according to the instructions @tiredoy. |
|
Here's the issue @igorbelikov I'm sure your build is fine but you could have added malicious code to send url/login/password somewhere before you compiled. Compiling your own application of Sequal-pro is not rocket science. Everyone that is not patient enough to wait for a release should just build the application themselves. It's only a few steps and can easily be done. |
|
@SteveMJones Of course, I, too, for self-assembly, I downloaded this build for those who quickly wanted to make sure that everything works or for those who are just too lazy. Because for example I had to install Xcode and spend about an hour of time on it. |
|
Release candidate is out! 🎉🚀 https://sequelpro.com/test-builds |
|
Eugh, clicking on relations does not work... |
|
@Kaspik it will cheer the day! 👍 |
Works well here. |
Is there a issue for this? I can't find it. |
It only works when you have the filterbar open (⌘F). When the filterbar is closed, it only redirects to the table but it doesn't filter correctly. |
Doesn't work for me, filterbar open or closed. This has been a bug with the prerelease version for a while. |
|
Problem for me with relations is it goes to the right table but it keeps the current filter text from the previous table instead of using the foreign key that I clicked on. |
No crash, but this issue is occurred when duplicate connection in new tab |
Confirming the above issue, seems to happen when switching tabs. Switching databases repaints the list and it looks fine. |
|
#bringBackTheOldTabBar |
|
General request: Please keep this conversation on-topic. Open new issues for any bugs/feedback that are not directly related to this bug ("Crash when closing a tab on macOS Mojave"). |
|
I have locked this issue. |
|
Please see #3705 |
|
Ref #3705 |
and others
Just create two tabs in the same window and try to close one.
Crash occurs
The text was updated successfully, but these errors were encountered: