Crashes under OS X quite regularly #1925
Labels
Comments
|
Looks like those crash reports got mixed up into http://log.sequelpro.com/view/2036 Also as the vast majority of those happened on Macbooks and there is a |
|
Sequel Pro crashes on my mac every time i press 'save' while connected to my db. I am connected via SSH. |
|
I'm also experiencing regular crashes of this type ... #1902 ... may be related. |
|
I've not been able to reproduce this issue. Note: Do NOT use a development build with production databases. |
|
I began experiencing this particular crash with the release of Nightly Build 4262 (in early February). |
|
@dmoagx I've been checking for updates every few days, and just spotted your note about broken nightly builds. I was hoping it was something like this and not a standstill in development :) The error occurs when switching between tables. The animated "Loading blah..." box appears, and the app hangs. Here's a recent Activity Monitor sample: |
|
I may have just figured out how to reproduce the error.
This crashes 100% of the time. If I skip step 3 or 4, no crash. The size of the Let me know if there's anything I can do to help! |
|
Hm, what is your setting on pagination of results? The sample above suggests the application is just idling. |
|
Limit results to 200 rows. |
|
@neokio Nightly builds are back up. Can you try a recent build to see if that works better? |
|
👍 I've been having numerous crashes too, specifically when switching quickly between databases. DB1 -> DB2 -> DB1 -> DB4 etc. |
|
Hi all! I'm on the latest Nighly Build (4285). This error is still 100% reproducible and very easy to cause. I don't really have any other large tables to test with, so I'm not sure if its specific to this db. I connect via socket to MAMP PRO 2.2 (MySQL 5.5.33). The tables are MyISAM.
... but the app is unresponsive, I have to force quit. Activity Monitor shows 0% CPU, so as above it's probably idling. If there are any steps I can take to help debug this, I'd be happy to :) |
|
Let's keep the discussion on "Query interrupted" in #1902 |
stuconnolly
changed the title
|
I'm hoping this error at least will have been addressed in the latest nightly (the specific "Query interrupted" issue isn't, but the backtrace for this pointed a finger quite strongly). If it's still happening I'd be very interested in an updated backtrace like the one at the top of the thread... |
|
I also found this recent crash log that might help: |
|
Has there been any progress on this? I get this issue semi-regularly, usually in groups where I can barely work for a few hours. I'm on build 4096. |
|
If you have a test environment, please try a recent nightly build from http://nightly.sequelpro.com/ and report your results. |
Closed
|
My problem went away when I changed job and got exactly the same model macbook-pro with exactly the same setup and installed the software from scratch (I didn't migrate any settings). Maybe something had gotten corrupted when migrating operating systems on my old macbook-pro on which I'd gone through several operating system upgrades. |
|
Closing after no further feedback. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is the crash report. It happens a lot particularly if I click from one table to another with a lot of data.
The text was updated successfully, but these errors were encountered: