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 while editing sql queries #108

Closed
qwesda opened this Issue Nov 1, 2015 · 5 comments

Comments

Projects
None yet
2 participants
@qwesda

qwesda commented Nov 1, 2015

I currently get 2 or 3 crashes a day while editing sql queries/functions. I've been using the 1228/1230 builds of Postico. The crashes seem pretty random, I haven't been able to see any pattern yet.

a) are there any log/crash reports that I should collect to help you debug this?
b) while the windows/connections restore quite nicely, the content of the sql pane is gone when the program restarts. It would be nice if the data there would also persist. This is probably related to #18 / #106

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Nov 1, 2015

Owner

There was a deadlock in the syntax highlighter that I fixed in build 1229. The issue resulted in a hang while editing queries.

If the issue continues with 1230 build, please email crash logs and samples to jakob@eggerapps.at

You can find logs in ~/Library/Logs/DiagnosticReports

If the app is hanging (spinning beachball), you can create a sample of the process with activity monitor. Select Postico in activity monitor, click the info button, then click "Sample".

I hope to implement #18 soon, which should also fix the problem of restoring the SQL query

Owner

jakob commented Nov 1, 2015

There was a deadlock in the syntax highlighter that I fixed in build 1229. The issue resulted in a hang while editing queries.

If the issue continues with 1230 build, please email crash logs and samples to jakob@eggerapps.at

You can find logs in ~/Library/Logs/DiagnosticReports

If the app is hanging (spinning beachball), you can create a sample of the process with activity monitor. Select Postico in activity monitor, click the info button, then click "Sample".

I hope to implement #18 soon, which should also fix the problem of restoring the SQL query

@jakob jakob added the started label Nov 1, 2015

@qwesda

This comment has been minimized.

Show comment
Hide comment
@qwesda

qwesda Nov 1, 2015

hmm, the ~/Library/Logs/DiagnosticReports is empty except for Postico_2015-10-07-215628_Daniels-MacBook-Air, which is too old. Maybe they aren't always written or they are deleted after are send to apple. I'll sample the process if I encounter the bug again.

It is possible that I was only using the 1228 build and that you already caught the bug.

qwesda commented Nov 1, 2015

hmm, the ~/Library/Logs/DiagnosticReports is empty except for Postico_2015-10-07-215628_Daniels-MacBook-Air, which is too old. Maybe they aren't always written or they are deleted after are send to apple. I'll sample the process if I encounter the bug again.

It is possible that I was only using the 1228 build and that you already caught the bug.

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Nov 1, 2015

Owner

It really sounds like the issue I fixed in 1229.

There are probably no crash reports since Postico technically didn't crash; it just got stuck while two threads were waiting for another. OS X can't detect deadlocks, that's why you'd need to sample manually.

Owner

jakob commented Nov 1, 2015

It really sounds like the issue I fixed in 1229.

There are probably no crash reports since Postico technically didn't crash; it just got stuck while two threads were waiting for another. OS X can't detect deadlocks, that's why you'd need to sample manually.

@qwesda

This comment has been minimized.

Show comment
Hide comment
@qwesda

qwesda Nov 1, 2015

makes sense

qwesda commented Nov 1, 2015

makes sense

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob
Owner

jakob commented Nov 4, 2015

@jakob jakob closed this Nov 4, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment