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

Crashes when opening local database #3460

Open
paragonsoftwaresolutions opened this issue May 3, 2019 · 8 comments

Comments

Projects
None yet
6 participants
@paragonsoftwaresolutions
Copy link

commented May 3, 2019

Every time I attempt to open a database after connecting to my local development environment the application crashes. I get the popup to submit the error, but that fails to send as well. After that it just sits at the Loading database screen. I have no issues if I connect to my product environment, only the local one.

@paragonsoftwaresolutions

This comment has been minimized.

Copy link
Author

commented May 3, 2019

Exception Error:
-[_NSInlineData isEqualToString:]: unrecognized selector sent to instance 0x6000002f43e0

(
0 CoreFoundation 0x00007fff44626cf9 __exceptionPreprocess + 256
1 libobjc.A.dylib 0x00007fff6f1baa17 objc_exception_throw + 48
2 CoreFoundation 0x00007fff446a0b06 -[NSObject(NSObject) __retain_OA] + 0
3 CoreFoundation 0x00007fff445c90ef forwarding + 1485
4 CoreFoundation 0x00007fff445c8a98 _CF_forwarding_prep_0 + 120
5 Sequel Pro 0x00000001000587cd -[SPTablesList updateTables:] + 1338
6 Sequel Pro 0x00000001000469c5 -[SPDatabaseDocument _selectDatabaseAndItem:] + 454
7 Foundation 0x00007fff467bc87e NSThread__start + 1194
8 libsystem_pthread.dylib 0x00007fff70bd62eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff70bd9249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff70bd540d thread_start + 13
)

@inigosola

This comment has been minimized.

Copy link

commented May 6, 2019

Same for me

1 similar comment
@thiagolte

This comment has been minimized.

Copy link

commented May 6, 2019

Same for me

@sojoudian

This comment has been minimized.

Copy link

commented May 7, 2019

same here

@D0zingcat

This comment has been minimized.

Copy link

commented May 8, 2019

same for me.

@abeger

This comment has been minimized.

Copy link

commented May 8, 2019

Same here. Running against mysql Ver 8.0.16 for osx10.14 on x86_64 (Homebrew).

Running version 1.1.2, Build 4541

Database was created via Sequel Pro, data imported from a .sql file and then a crash. Progress bar never updated, but percentage did. Looking at the DB from the command line, the data appears to have imported correctly, but any time I try to access via Sequel Pro, I get a crash as described above.

@sojoudian

This comment has been minimized.

Copy link

commented May 8, 2019

this issue is caused by some variables which mysql 8 is return and sequelpro is not compatible with them. So, use the latest test build which is working fine with mysql 8 from : https://sequelpro.com/test-builds

@abeger

This comment has been minimized.

Copy link

commented May 9, 2019

That fixed it for me!! Thanks!

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