Developer

installing update and clicked "Install & Relaunch"

i closed my mac, and when i reopened i tryed to use sequel, it crashed

Cancelled a somewhat longer running query. The "Query in progress" hud thingy was displaying

viewing a table in content tab

tried to reconnect

/*!40000 ALTER TABLE `tx_w2ptubetransfer_files` ENABLE KEYS */;
UNLOCK TABLES;

Tried to do this on a 10000+ items table.

I quit SequelPro while reconnecting to a database after waking up my MacBook from hibernation. Weird, i know ;-)

opening information_schema.statistics table on a db server where it contained more than 16.000 rows took me too long, so I pressed 'stop query', but then it hanged

reconnecting via ssh.

- cpu to 100%
- new certificate sheet appeared, unlike when there is a new connection being made the sheet buttons do not respond to mouse clicks or keyboard
- the standard modal dialogue box asking to "Reconnect" appears.
It responds to mouse and keyboard. It will even act on the keyboard input that the new cert sheet ignored.
- Finally I "Disconnect" and command Quit

quitting Sequel Pro after real interuption to network connection to DB.

FIrt click on "stop Query" in grey query working box, then 1-2 minutes later
cmd-Quit app

I was loading a table, then it started the spinning 'Loading table...', then crash

Just froze after converting MyISAM to INNoDB

Creating of an index seamed to time out jn gui, on command line the action was already done

tried to stop a query

connected to a remote server, started beach balling while reading db information, force quit it after 10 seconds

abort an sql query

cmd + q while sequel was thinking.
the server i was connected to was not responding (very quickly)
to all connections (not just sql)

did i manage to reproduce the pinging issue?

jakob

big query

BIG Query. Dumb Query.

a query was running on a remote server
I unplugged de network cable
then clicked on the "stop query" button
crash

stopping large query to a table

Loading large table with blobs not deferred. Clicked "stop" and button greyed out, but it did not stop. Didn't feel like waiting.

added an index

trying to reconnect

Select table with 120k rows over DSL, click stop after 1/8 progress, crash /dogx

See above, reproducible /dogx

I killed a long running query which seemed to hang, but that didn't work fast enough for me, so than I just quit sequel-pro (via cmd+q); next thing was the crash...

Run query with 3+ joins

I stopped an ongoing mysql command while fetching the data

filtering results

stopped query

canceled a standard "Content" select * statement that was running too long.

truncating a table

lo abri por primera vez y salio esto

Hit the stop query button while a query was executing

tried to open a table with large data fields

break query

anytime i close the computer without ending sequel pro, it crashes when I come back. it does give me the "reconnect" option, but it never works, and just hangs so I have to force quit each time this happens.

Anytime a query takes too long and I cancel it, the application quits.

cancel query

fucked a dead horse

Quit the application

Queried a 4gb database

Opened my macbook pro and clicked refresh on the table

A query with a massive number of results

Put the laptop to sleep, moved to another location outside the network, switched to Sequel Pro and exited the application. It crashed while exiting.

tapped 'STOP' while a query was running. Server is mysql 3.23

I've pressed cancel on "content" tab to stop fetching and tried to sort by column

ssh connection dropped

put laptop to sleep while running query

Clicked cancel on a query ran from the query window

i opened a session and that session probably expired. window was open for last 6 hours. I tried to run a query and instead of asking me to reconnect it crashed.

There is a work around i have found to make it work. If you hit stop query as soon as you start running the query and select "reconnect" on resulting box it works. Outside that work around it crashed every time.

hit the "Stop" button for long query

Still trying to load a big big table (36 000 000 records)

I wanted to add a extra Screen >> File > New...

Clicked Stop Query

My network configuration changed, while a DB connection was open. 100% reproducible crash.

Sequel Pro always crashes on me if my computer goes to sleep while Sequel Pro is running. When I wake the computer back up, that is when Sequel Pro will crash. I often change internet connections via different wifi hotspots, so this may have to do with it as well. Thank you all for such a great product!

Tried to stop a running query.

INSERT INTO `Language` (`lang_id`,`name`)
VALUES
(1,'Inglés | English'),
(2,'Español | Spanish');

Attempted to stop a running query.

i hit stop query when a long query was running

stopped a query

Connection timed out, Sequel Pro crashed after trying to cancel query.

Clicked cancel on the "filtering table" popup (twice now)

opened the program

opened a large table

Just quitting the app.

Stopping a query

Stopping query

closing it

probably slow server response
sequel didn't handle it very well so i killed it

Disconnected from the network with a connection open. Reconnected to the network, clicked on Sequel Pro, then crash. This happens all the time. It really does not like network disconnects since the most recent update. Let me know if I can help with resolving this.

Closed after installing.

Cancelled a query

listing large table over slow link.
While table rows were loading, I reduce the 'limit rows to' variable from 200 to 50 to avoid this slow loading the the app crashed.

clicked stop while listing table rows over a very slow link (SSH).
App crashed.

running a bind param from php on 5600 rows

I changed wifi network while connected to a database and didn't discconnect before leaving the old network

Canceling a long query

I hit 'stop query'.
Nice.

ran a custom query

stopped a query which was taking long.

stopping a SELECT query

Connexion to a Database thrue a slow VPN cnx.

I tried to load 80k records at once from a remote 4.x server, and then hit "stop"

Refresh of a table but changed connection. Squel Pro hangs every time a go from work to home without quitting Sequel Pro.

I keep the application running while changing network.

The Connection is very slow so seqpro keeps crashing.

sorting on a column

opened my macbook pro from sleep waited for my internet to reconnect, then hit cmd+r to refresh the table that it was already viewing from the day before

opened laptop from sleep mode cmd+r to refresh table view

I moved to a different wireless network. Sequel Pro always crashes if I close my macbook pro while on one network and then re-open it on another network.

I was trying to sort a table using a column. It took too long so I hit STOP. The program crashed

Running a large query, and canceled cause the application to die twice in a row.

Tried to view the structure of a table over an SSH connection. Hung for a long time - couldn't find a way to cancel, couldn't quit, had to force quit.

just changed database within a single connection

I had an old Sequel Pro window open that was disconnected, so I went to File -> New and when the new window popped up.. I closed the old one behind it and that's when the crash occurred.

BUG REPORT:
When I put my macbook to sleep with an open connection and later I wake it up and try to execute a SQL query it crashes everytime.

After laptop back from sleep, connection to server must be broken - trying to select table - received a crash.

could someone pleas email me @ aegrant@gmail.com about these incessant crashes?

I was running a simple query with one join and it froze up after it started displaying results. This has been happening very regularly since the latest update. If there is anything else I can provide to you I will gladly do it as Sequal Pro is now highly unstable for me.

Quit

I stopped execution of a query which was running too long; I'm connected via my mobile provider, and I suspect my internet connection caused the crash, because the gprs-connection just switched to umts moments before the crash

closing it, jesus christ.

Tried to stop/cancel a query from running

Tried to stop a running query.

ran a really bad self joining query and then hit Stop Query as it never finished. Then it crashed.

forced quit it after it would could not open a database

cancelled opening a view

tried reloading a table after computer was idle for a while.

selected the STATISTICS table from the mySQL database while viewing the Content tab.
app appeared to hang with the progressIndicator spinning.
I waited 30sec or so before quitting

every time i try to stop a long running query the application crashes

tried to connect to a busy data base. took too long. quit.

woke up laptop and quit sequel pro and it crashed as it was closing

Trying to reconnect to a database after the connection had died

cancelled a slow query

Closing a window

I was loading a table on a database that had a separate process importing data to it.

woke macbook from sleep. crashed as usual

I get little hang-ups & freezes sometimes, but this time nothing was wrong, I just quit the program and it called that "quitting unexpectedly." Oops!

Stopping a query taking forever.

cause the app crashes.

I had a query that was taking too long so I stopped it.

switched wireless networks, woke from sleep, activated sequel pro. Apple-Q. Crash.

Attempted to stop loading a table with around 32000 records x 20ish columns

I clicked the STOP button when it was loading a very large data set in the 'Content' view.

Attempting to open a new database connection.

Tried to connect to a database as root when I think root did not have explicit access. The busy display came up and I could not stop it. I tried to exit and that is when it crashed.

stopped query that was taking too long

I aborted the opening of a (for me) large database (> 10.000 tables), then sequel pro crashed

exiting the application

killing a query

closed the program after macbook resumed from sleep or standby

I switched from one database to the other

cancelling a cross join query on a remote server through ssh

Reconnect ssh

Slept computer while connected, woke up computer from sleep and tried to close the window for the connection

trying to view a table with content view after the session probably timed out

Ran a query, inner join across 4 tables

Stopping a query when it is executing causes this problem

RAn a query after coming out of sleep mode

stopping long query

Tried to connect to database

tried to stop a slow query

Opened my MAcbook Pro and cmd+r to refresh the table. It hung and crashed

Opened a table
Then pressed the stop button on the progress window

error

ran a long query while connected over SSH

frackin crashed due to a timeout with the db. When the hell are you guys gonna fix this?

Can't remember.

The database connection timed out, and I had to force-quit because the program locked up. This is a recurring problem.

Tried to preview a huge (10.5M+ rows) table

ran a query that was too long - tried to cancel

Woke computer from sleep, then quit Sequel Pro. internet was disconnected at this point.

Running a SELECT query on a relatively small table, battery was running low.

opened a big table

Hit "stop" when it was loading a large table

finished export

stopped a query running on a db with lost connection

I seem to have the most trouble when I've got a window that is connected via ssh.

had my laptop closed overnight,opened it, signed in and tried to connect back to a database. sql pro froze up and had to be shut down by force. This is a common problem with the software

custom query, cancelled it a few times, wifi on a train

stopped query after waking from sleep, no reconnection made

Connecyion lost to internet.

The network connection died and I quite SP using [command][q]. This was an ssh-connected database connection.

Tried to load page 30,000. Realized that it would take a while, pressed the stop button on the popup box.

trying to reconnect to a db after waking up from sleep mode

disconnected from internet

Nothing, just returned to Sequel Pro. But the internet connection was down.

load a table data (in the contents tab)

stopped a long-running query connected to a mysql host via SSH. This always happens.

clicked stop query after running a query without a where clause on a decent sized table.

Lost network connection while query was executing. Clicked 'Stop Query', the button greyed out and it just hung, with spinner going constantly.

tried to cancel query

Crashed, likely do to the flaky network at WWDC.

nothing

Stop loading data

failed to stop a query and i forced a shutdown

BTW sequel pro frequently locks up with high CPU usage. Only this version

Run a large inner join query and tried to stop it.

opened the program

Ran multiple queries

I was in Table Info view on one table and clicked to select another table. It displayed the Loading... spinner for ages so I tried to close the viewer window. That caused a spinning beachball of death so I Quit from the Sequel Pro menu, at which point it crashed. I've switched tables in Table Info view plenty of times before without a hang up.

During long query, I hit the stop query button. Here was my query:

SELECT exp_weblog_titles.title AS title,
exp_weblog_data.field_id_4 AS description,
exp_weblog_data.field_id_8 AS street,
exp_weblog_data.field_id_12 AS phone,
exp_weblog_data.field_id_14 AS url,
exp_weblog_data.field_id_15 AS hours,
exp_categories.cat_name AS city
FROM exp_weblog_titles
INNER JOIN (SELECT exp_weblog_data.entry_id,
exp_weblog_data.field_id_4,
exp_weblog_data.field_id_8,
exp_weblog_data.field_id_12,
exp_weblog_data.field_id_14,
exp_weblog_data.field_id_15
FROM exp_weblog_data) exp_weblog_data
ON exp_weblog_titles.entry_id = exp_weblog_data.entry_id
INNER JOIN (SELECT cat_id,
entry_id
FROM exp_category_posts) exp_category_posts
ON exp_weblog_titles.entry_id = exp_category_posts.entry_id
INNER JOIN (SELECT cat_id,
cat_name
FROM exp_categories) exp_categories
ON exp_categories.cat_id = exp_category_posts.cat_id
WHERE exp_weblog_titles.status = 'open'
AND ( exp_weblog_titles.weblog_id = '4'
OR exp_weblog_titles.weblog_id = '2'
OR exp_weblog_titles.weblog_id = '3' )

Tried to stop a query

selected "quit" from the dock context menu

ran the installer

reconnecting to a db after being asleep

was closing app

query ran for a long period of time, so I clicked "Stop Query." The running query box did not go away, so I quit Sequel Pro and it "crashed"

download & install - auto reboot - then crash

I tried closing the window. I was logged into a server via ssh.

querying an ssh server - always crashes when i've connected a session over ssh :( always :(

Stopping a long running query.

Ran a left join from a million row table to a 10,000 table.

Clicked the stop query button

trying to close an unreponsive connection

edit table structure

quite

running a query over a ssh tunnel

Tried to cancel a running query over ssh on a wifi network at the SLC airport, probably pretty spotty

canceled a query

Tried to create a new window for opening a database and accidentally clicked another Sequel Pro Window and moved it and then crash.

nothing

run a double subquery query

Automatically reopened: new report received from a revision after this problem was believed to be fixed.

running a simple query, was taking too long. tried to quit the app, then it crashed

Canceled a long running process.

shut the application down

vpn connection to db was lost; sequel crashed.

Clicked the button to stop running a query on the Query panel

Changing DB's

Ran a long running query, then quickly hit the stop query button.

Tried to stop the load of a large table.

I hit the 'Stop query' button in a long query

Cancelled a long-running query

returned from sleep

mySQL server was disconnected and restarted

crashes all the freakin time now!!!!

attempted to stop long query

Uploading sql dump to external server, program crashed on multiple occasions

restore from hibernate

When canceling query

Accidentally quit with an UPDATE query running

stopped long query

stopping query

Interrupted a long-running query

Switched back to a previously opened window

Just querying a huge (>1.600.000 records) table

Closing a window.

Canceled a long running query...

Closed a window

Cancelled a query which was still running.
Connection was over a slow ssh tunneled connection.

attempted to close the application

stopped a query while in progress.

Disconnected my VPN session

SELECT s.name as service_name, SUM(IF(um.new=1,1,0)) AS new, uf.* FROM user_messages um LEFT JOIN user_friends uf ON um.username_id = uf.username_id AND um.user_id = uf.user_id AND um.service_id = uf.service_id LEFT JOIN ref_services s ON uf.service_id = s.id WHERE um.user_id = 1 GROUP BY username_id ORDER BY date DESC LIMIT 20

ran a query

I had changed networks without closing a session window with a server. I did not try to execute anything other than immediately trying to close the window by clicking on the red button in the upper left. This hung and crashed Sequel Pro.

ran query that caused "out of memory" on server

i ran a query... sigh

tried to reconnect after waking from sleep

Just switched to a different DB. It hung with the progress spinner on screen, so I hit CMD-Q.

trying to stop fetching records from a table with the stop button

logged in to a database on a local network

logged on to a database again

virtualbox with ubuntu9.10 failed (overload cpu-usage by apache2)

started to run a fairly standard query that I've run many times before.

Stopping a running query

Force quit-ed it as I had just freezed my virtual machine containing the mysql server I was connected to. It didn't freeze/crash or anything, I just had to quit all my programs really fast :p

Keep up the good work, Sequel Pro rocks!

left join queries over big tables

your mom

delete from votes where created_at >= '2010-07-05'

execute a simple querie

Ran a query on a remote server on a VPN, closed the VPN connection, then clicked "Stop query".

Trying to stop a long running operation.

executed some long-running queries

I quit the application

I was opening a table with 126000 records and when i tried to stop the process, BAM! there he goes!

Tried to add some indexes to a remote database. My connection is not very stable today.

your software always crashes!!!

Switched to another wifi and tried to reconnect

Program quits when telling it to perform a query after the connection times out - fix should probably have it double check for connection, then re-establish if disconnected prior to attempting to query.

tried to quit

stop long running query

Start a long running query; try to stop that query using the "Stop query" button on screen. (Well, it *does* stop, I suppose....)

open large table

stopped a long-running query.

Stopped a table loading.

Stopped a query

Stopping the same table from opening

Query took forever, so I closed. Then the app crashed.

reloading data after computer sleep

canceling query

this query caused the crash select distinct(concat(Type, ' ', Kind)) as name from PossibleUses group by concat(Type, ' ', Kind) it was the addition of group by concat(Type, ' ', Kind)

Quit

add index to column

reconnecting to db

I was just opening a table.
before i create / delete a table (several times) of 16000 entries

lkj

Tried to open a table while in the query window

select data

reconnecting to db ... again

Clicked 'stop queries'

tried to quit application after a Virtual Machine hosting the connected database was shut down.

ran a query.

Quit SP that was trying to retrieve information about a table that appears to be in error.

closed a single window

Stopped a table from loading

query

stopping a query

Just trying to fetch data from a database.

Changed the table, I think the VPN may have dropped for a second while I was changing between tables. Thanks

Remote database went down, I believe is what trigged this condition

pressing the "stop query" button while running a long query

se nun ce siete bboni, ditelo.

loaded the application

Was Running a query that I realized would not work. When I hit stop query, Sequel Pro crashed.

Cancelled a long running query.

I ran a query on a remote database

cancelled a query

tried stopping a laaaarge table from loading its content

ordinary quit

reconnecting to a machine

tried to stop a query

Trying to hit the 'stop loading button' while loading a table with a lot of XML

Tried to stop the loading of table data.

Stopped a *VERY* slow query from being executed.

changed IPs (dev connectivity testing)

just can't handle big tables

kjhgjkhghjkgjkhg

Trying to view structure of a large table. If structure is the view, data shouldn't be loaded.

woke the computer from sleep

I was trying to open a table Content for the table that was still loading into DB from backup. This took to long, so I decided to just Command + Q out of Sequel Pro :)

Disconnecting then reconnecting network.

Lot of rows

Nothing, just started the app

tried to stop a query which was running long

Cancelled a long running "Content" retrieve.

clicked stop when loading a lot of data

locked few tables

Crashed while stopping a sorting.

attempted to reconnect after waking from sleep

the connection was droped

command tabbed back to sequel pro from safari - had 2 connection windows open in sequel pro - one to a localhost and one to a webserver

Hmm... not sure

stopped a query while it was executed

Close two windows with Command + Q

Add a primary key to a table.

closing app

Pressing Stop query

deleting a lot of rows from a large table

ran an update statement

Network went down

closed a browser after computer slept

Was connected to a server, closed laptop and went to coffee shop, reopened and was just closing the window, no big deal.

The network went away and came back after opening a connection. The window was open and I tried a new query. Reconnecting did not work.

just executed fucking ....

closed the window

hit stop on load of large (20k+ rows) table over terrible wireless connection (<10k/sec)

Network connection was disrupted.

deleting the content of a table. its about 30mb.

closed it normally

the data don't load and when i click stop a crash occour

I clicked stop query

a big sql involving mathematical operations on a big table. sorry

click on e view

adf

Ran a (larger than it should have been) join, then tried to click the "stop" button on the spinner dialog box... didn't like that much.

chrashed durint this query

SELECT DISTINCT count(*) total
FROM fiatc_dades_personals fdp
, fiatc_municipis fm
, fiatc_provincies fp
WHERE fm.id = fdp.poblacio
AND fdp.provincia_id = fp.id
AND carrer_personal NOT IN
(SELECT DISTINCT carrer FROM fiatc_geopoints WHERE lat IS NOT NULL AND lat != 0 AND carrer != "");

Ran a query and then clicked Stop

Tried to close a remote connection after waking my mbp up from sleeping.

Automatically reopened: new report received from a revision after this problem was believed to be fixed.

Try to close the program

I just closed it yo!

quit unexpectly

tried closing a connection using command-w

running an SQL statement

Sequel Pro constantly crashes...

And take a look at MS Sql Server Mgmt Studio and attempt to emulate some of the features. That is the one tool Microsoft got right.

intnernet died

canceled a running query

a

i had two connection windows open to the same place, then slept my computer. woke my computer up, and then quit and got this message

filtering large table

jiminoc

still filtering tables. crashes every time now.

jiminoc
reconnecting to db

I started a Query which seems to run in an infinte loop and clicked on "Stop Query". The stopping of the query didn't work. The "Query is stopped" window stayed for minutes until I shut the program

Crash.

ran a basic select query against a database hosted on another server. Our network is a bit spotty at the moment which could have been part of the problem

stopped a query that was going to return to many results

tried to delete an index... app froze up... might be because another user was inserting a lot of data in the table concurrently.

Tried to quit, a connection to a remote DB was still open

cancel a query that is taking a long time. and it close on me.

using a snow leopard

mysql server hung up and there was no graceful way to abort the connection in sequel pro.

Just tried to load up a database that I've loaded a hundred times before. Nothing unusual.

Attempted to add a unique index to a larger table (27k records)

rebooted

Closed with a stale connection

stale connection problem again

gimme a break. the crashes are ridiculous.

stopped a query which seemed to take a while but most likely the connection timed out. while de query ended allready at the server.

canceled a load of a table with to records with a large BLOB in each

Quit while a query to a dead server was stopping.

double click on a table with 1mil+ rows. mysqld restarted.

I clicked the upper left red x to close a window/connection, and then hit command-n for a new connection, before the old window/connection managed to close.

Loading a very large table via ssh, hit the stop button to stop it loading

tried to run a query that was probably too hard for the system

My internet went down while it was trying to load up a table... and I had to kill the program because the request didn't time out. There needs to be a way to bail on the table loading, or at the very least a timeout.

Tried to sort a column on a remote connection after waking computer up from sleep. I know it loses the connection, but usually it asks me if I want to reconnect. This time it crashed. No biggie.

Did not disconnect from DB before "sleep"ing. Quitting on "wake" up on a new IP/net without access to previously connected DB caused "unexpected crash"

left computer open, then crashed on reopening

Selected a table thru an ssh connection - nothing really to report... ah found the issue. My internet bombed so don't be alarmed. no dragons here.

PS Love your work!

killed a query

Reconnecting to a db via ssh after awakening computer from sleep mode. Seems to be consistent in failing to reconnect and usually hangs the app.

When I lost internet connection during a query

executing slow query, hit "stop" button, had to FC the app.

deleting a table

network connection went down, took the program with it

Submitted self-join query on 12,000,000 x 150 table, query hung, had to force quit.

I am using Sequel Pro over a VPN connection. The program seems to timeout if left alone for too long without any activity. when it prompts to reconnect it usually does and continues to work. Sometimes it tries to reconnect and just hangs

closing app

Tried stopping a query

Tried to stop a query.

tried accessing a table in a database

I had 2 databases open. One remote, and one local.(standard/socket respectively). I had many applications open and I was just Cmd+Tab+Q'ing through them all. All other apps had quit except this one. It then crashed. I will try to replicate it next time I close.

nothing, it just crashed

cmd+q

delete column

sitting idle

CREATE TABLE Test (
enmTest ENUM ('a', 'b')
);

INSERT INTO Test VALUES ('c');

closing squel pro while it's waiting on a locked table

added 2 cols to a table named country and category

internet connectivity lost

Tried to close a database connection. The connection was obtained while using wireless, but I switched back over to ethernet connection prior to closing connection.

I had it sitting for a while, not interacting with it. Then I tried to click on a different field and it could not connect. Clicking retry made it stop responding...

Renaming this issue for a bit of clarity.

Basically, vio_delete is crashing when releasing some of the connection details (I think). This may be because the connection is being over-released, or may be because other threads are still using the socket in question - it's not very clear yet.

I've added some more checks in r2591 to see if it's an over-releasing issue, we'll see if it keeps recurring.

Title changed to "MySQL client library vio_delete crashes".

Close the existing window after computer woke up from sleep

Ran a query

long running query...

Loaded a large dataset accidently

Went to sleep, came back from sleep and quit.

The computer went to sleep. Woke up in the morning and did a quit from app bar

select on 2gb - 80million row table, example

select count(xxx) from aaa where xxx >= 12000

Was working on a large-ish table (80m rows and about 2gb in size) guys you might wont to know that I am crashing very regularly every day. I have the max number of rows reduced to 1000. However the crashes are occurring when I run manual queries...

It has been several days, so I have no idea what happened the last time Sequel Pro quit.

Nothing

I canceled a Query after Sequel Pro lost the connection to the database.

I tried to quit with Cmd+Q.

I selected a table with a huge amount of entries.

I just selected a table from the right panel [Select Database] (the table has a huge amount of entries)

reconnecting

;kljhasDKLJHASDLH289389238934/344$$$$$

O

lkhjlkj

We've updated the background ping logic to improve threaded keepalive behaviour, and this should address the issue.

Status changed to "Fixed". Marked as fixed in r2602.

Loading items in large table that was probably receiving new entries (loecked exclusively).

Trying to quit while large, externally exclusive locked table was loading.

stop a running query

Accidently ran a DELETE ... WHERE instead of a SELECT ... WHERE. Hammered "Cancel" and then crash.
Machine was newly (4 minutes) woken up from hibernation; re-used existing window/connection over MySQL protocol.

Refreshed table content

reconnecting after sleep

Tried to switch active database

Automatically reopened: new report received from a revision after this problem was believed to be fixed.

Seems that the app hangs/crashes sometimes when editing a row via the content view... I think this might occur if a select takes place on the row at the same time perhaps.

trying to load a huge table

connected over vpn.
ran query
vpn connection dropped before query started.
reconnected to vpn while query was trying trying to connect
click on stop query
program crashed

Loading a view

Had problems with Internet connection, was very unstable

Tried to stop a long running query. It kept running, leaving the connection window useless. Tried to close the window -- unsuccessfully. Upon quitting the program via File->Quit, it crashed.

Lost internet connection

just tried to connect

closing the app

opened sequal pro

Network connection crapped out. Sequel Pro was mid-query and crapped out as well.

tried to quit Sequel Pro while it was hanging running 'show processlist'

I've tried to cancel long running query

launched the program

query was running

Tried to reconnect, after closing my laptop and moving to another wifi

clicked 'stop' on a filter that was running

my network connection failed

cancelled a query

quit in the middle of a long-running query

Canceled showing the content from a 85mb table with two mblobs via SSH db connection

Stopped a long-running query

stopped a query

sort massive table on a non-indexed field (tinyint(1) )

Closed application in the middle of a long query

just tried to load a table, this keeps happening probably half a dozen times a day.

I had just done an export from a live database offsite on a shaky connection. The export seems to be fined, the program crashed when I tried to close it after the export was complete.

clicked 'stop query'

Pushed ENTER to search by ID

reconnecting to db

loading a table

ujh

I did a SELECT * on a table with about 350.000 records

clicked on a table while it wasn't finished importing from the command line :)

I just opened the app...

please Help

plugged in ethernet cable and turned off airport, since wireless was wicked slow...

SHOW full PROCESSLIST

below is results of SHOW FULL PROCESSLIST.

i tried to view a table that is undergoing a repair (see id 9) then tried to quit application as it was taking too long then app crashed (you can see the app access attempt in id 6 & 11)

cheers
jon

6 root localhost:49437 epf_app Query 886 Waiting for table SHOW CREATE TABLE `m_application_price`
9 root localhost epf_app Query 3582 Repair by sorting ALTER TABLE m_application_price ENABLE KEYS
11 root localhost:50455 epf_app Query 66 Waiting for table SHOW CREATE TABLE `m_application_price`
15 root localhost:50470 epf_app Query 0 NULL SHOW FULL PROCESSLIST

accessing a database over ssh

reconnecting

quit the program. My internet connection failed, so the program hung.

Seems to crash when it loses it's connection and you try running a query

db slow connection

Quit...

canceling of a sort pocess for a view

Paging through tables with large fulltext fields

Query took to long so I stopped it I believe.

Killed a long-running query.

Quit the program whilst it was loading a new table

Ran a query on a table that had over 1.5 million rows with a slow internet connection

Quit while trying to reconnect to a remote host

SSH access

I did nothing, I just lunched it and it ,,,

connection had timed out

Try to use open Sequel window after changing internet connection (laptop went to sleep before disconnecting from internet, ethernet port, and connected to wifi upon wake up)

left on

the fucker died

I did an export of three specific tables and then tried to refresh a completely different table 'Content'

I just opened it

used the program.

My ISP's routing tables had some errors and connection the server was dropped. At first I didn't know this, so I pressed reconnect, which caused Sequel Pro to crash

Having trouble importing SQL dump. Sequel Pro locks or quits unexpectedly.

Quit the program when computer back from sleep.

changed name of database. i think...

just quitting the application is all!

Hit Cmd+Q to quit the app.

Load a table

closing windows

close a SSH connection

run a heavy query

pressed "stop" while loading table content

reconnecting to a server

sorting a 70 million row table

Switched ip-address while logged in

Tried to stop a long taking table filtering.
2-3 seconds after i hit stop Sequel quit.

tried to cancel a running query. The ssh tunnel had lost its connection so after I clicked on cancel query, a box came up asking about the connection, I clicked reconnect and the application crashed.

I clicked on "Stop query in progress". This happens almost every time i try to stop a query which is running and almost always it is after i have lost connection to the DB and the query is just timing out but ends up hanging

trying to stop a running query

Woke up computer, re-ran last query to see if Sequel had reconnected, canceled query after 10 seconds as Sequel had apparently lost connection, the cancel button turned white, the app hung for about 3 seconds, and then crashed

switched to a new table after a long period of idle time

I quit the app as it was trying to connect to a database.

Forced-quit while waiting for long-running query to cancel.

lost connection

ran a query

Attempt to close an ssh-tunneled remote db window after awaking from sleep.

shut down computer

CHecked for an update

reconnecting as always

tried to cancel something

connection dropped, when i came back i tried to keep using it without explicitly reconnecting first; program always hangs when i do that. it's actually like 100% of the time, as if it were a feature and not a bug; so if you'd like to resolve this issue, my otherwise-flawlessly-functioning (except for one common/widely-reported Adobe CS5 issue) machine could be a good environment to look at. email me.

disconnected ethernet before quitting Sequel Pro.

I stopped a running query.

canceled a query on remote machine

opened my computer from sleep, waited for wireless to connect, then hit refresh. The application had previously been left open in table content view.

Tried to stop a table loading process (500 rows limit) of a sequelpro.com server connection over a very slow connection

waiting connection to reconnect to server

i simply didn't use sequel pro for a while. i think the computer might have hibernated.

Running a query, lost connection to database.

aborted a slow query

i closed my computer, left the office, went home, and tried to load a table, and it hung. sequel pro has been hanging upon first attempt to access this particular DB a whole lot. It's a database running phpmyadmin, and it's a very simple setup, so while it's quite likely we're not doing everything exactly right... it's also a very simple setup using many of the defaults, so I'm not sure why it shouldn't work.

Quit the app while connected to an ssh database

switch network while sleeping

Frezze

Was wotking with multiple windows

tried to view contents of a table with very large values in it

quit while hung after clicking on a table.

quit while hung after clicking on a table in UI.

tried to cancel a sort

very bad quality in snow leopard

Changed network connections. Ethernet to wireless.

same as usual: left session open while my computer hybernated/slept, came back, clicked one of the tables on the left to see its content/structure, and the thing hung on the "loading table" whirligig. so I quit, and instead of quitting it crashed.

ran a query. Looks like it took a look time, and Sequel Pro has a habit of never returning from long queries (even if the DB does return)

Open a database table

Tried to quit the application while it was trying to select a new DB.

I don't remember :(

Anything, this program crashes all the time.

evertime i resume from sleep i have to close and open this again.

dumping a database (through ssh+mysql) and connected in an other window to the same server.

closed sequel pro when connected to a db

attempt to log in to unresponsive server

I accidentally disconnected the network before quitting. Maybe it panics if the db connection goes away?

one of the databases was corrupted

quit?

My router was turned off

i canceled the transaction (receiving data)

I just started it, after connecting it doesen't show infos of database and after 10 seconds it crashed

ran the following queries together:

drop mydb database;
create mydb database;

Was running a DESCRIBE on a complex query on a MySQL server in a guest virtual machine, and the virtual machine crashed, wreaking untold havoc on everything connected to it.

run a query while the system downloiads updates

running a query

i was looking at a table that was deleted through the command line.

cancelled a running "LEFT OUTER JOIN"-Query

Laptop went to sleep whilst an SSH connection was open

Executed a simple select query, query was taking much longer than expected, was unable to end it by clicking "stop query". Could not close Sequel Pro by any means other than force quit.

hit stop query

fucking A!

Using Sequel Pro on an unreliable VPN link

Running a big query, when attempting to stop it, it crashed

delete orphaned rows left outer join on a 1.5MM row table.

After an hour, I noticed that memory usage was 56MB, which seems way too low to efficiently run the query.

Sorting a large table over SSH, and then pressing stop. Sorry.

wake up after standby
sp asked for keychain access
denied
(I quit SP(?))
crash

/dogx

Attempted to add index via content view's "add index" button. "Adding Index" dialogue box was shown for several hours. Clicking "stop" did not end the query and no interaction with the GUI was possible.

save a query and then quit the application

closed the window

running simple sql query. This is getting annoying!

running a simple query

hmm...

I've sent some query to mysql DB, then I got realized, that tables don't have indexed and decided to stop query.

'Stop query' button waz too lazy, then I pressed Command+Q, and so we are...

Nevertheless, the program is cool, thank you!

Tried to close app when it was trying to connect to local mysql server.

program tends to crash when the same session gets disconnected over the course of a few days

Running small query on networked volume

Just closed it

Long period of inactivity and then trying to refresh table

I changed a Favorite and saved it as a copy.
/etc/hosts holds an entry that differs from what hosts would give

reloading FEDERATED table

Run a query on a table which was taking a long time so I stopped it, then clicked on the same table in the left sidebar and that too was taking a long time to load so I tried clicking stop again and the app just sort of came to stand still

renamed a column in the GUI. It so happens the table was locked by another query. While the progress indicator was spinning, I hit cmd-q. then the app crashed on quit.

I was sorting by a column and kaboooie!

Accidentally clicked on a table that was being populated with data from the command line.

Executed simple query on remote server on local network, but network connection was lost... (i was connected via wireless)

Stop a query

I had unhooked from network before I quit SequelPro

Tried to stop a query

start the program

ARGH MATEY!

jsut running a query

it was trying to load a content preview of a table, I hit the stop button, then teh structure button. then kaboom.

Started computer from sleep. When I tried to close one window of the program it crashed.

launced it

lost network, closed connection, application crashed

tried to filter a table content using the "contains" field. realized too late that the table has 2.1 million entries and a LIKE search would take quite a while. so I tried to cancel the query (pressed the 'cancel' button). but nothing happened and after about half a minute Sequel Pro crashed. The database (mysql) is on a webserver.

Quit application while it was still busy aborting the deletion of an index.

PC came out of sleep and then I tried to close Sequel Pro and then the crash occured.

ran a query on a database to which I was not connected

reconnecting

I stopped a filter and the app crashed.

broke

I put my computer to sleep overnight, and came back to a remote connection and tried to interact with the data

Quit during a reconnect. Always seems to crash when I do that.

it crashed upon a MySQL db timed out.

stop/cancel table from loading all rows.

My Mac was connected with an ethernet cable to the Internet and Sequel Pro was connected to a remote MySQL server. I activated sleep mode on my Mac and moved it to a wireless network. During this time I also ran the command "mysqladmin flush-hosts" on the MySQL server. Later I woke up my Mac and quit Sequel Pro and at that point Sequel Pro crashed.

Loading a large table, 6 gbyte approx...

searching on table names

I was closing (command-q) the program. I had a connection open to a VM running on my machine, and I closed the VM before closing Sequel Pro. So SP was "open" to a computer that was no longer accessible when I tried closing the program.

Had connected to a remote MySQL server via ssh. I chose a database and Sequel Pro started to fetch the db info. The MySQL server locked up and after a while I tried to disconnect by closing the window. That did not work. Then I tried to quit the app and that resulted in a crash.

stoping remote query

preformed a large query

stopped a table from loading

Hello,

I often run queries in the "Query" section of Sequel Pro, however it fairly regularly will hang, so I have to quit (sometimes force quit) in order to get out of it. As far as I can tell there are no errors in the queries I write (once I log back in I'm usually able to run the query with no issues).

Thanks,
Steve

Changed Database after long period of doing nothing

opened laptop and tried to use application

running a rather ugly query - I think my vpn connection hiccupped while it was going (vpn to office, connected to db over ssh tunnel)

Close Connection and then i hit quit

just loading a table after clicking it and the app froze

loaded table data. it was taking a long time to load (much longer than in the previous version of SequelPro), so I clicked "Stop" on the loading dialog. Then it died.

I tried to stop a query

working with federated table in error state

Trying to load a table via SSH connection and it hung, so I quit normally. After which, it then reported the crash.

Ran a search on a large table (~2 million records), saw it was taking too long so I hit the "Stop Query" button. When the spinner kept going and the app became unresponsive I quit out of the application.

Tried to run a qry. The window was minimized for a while. This happens a lot. I ran the same qry in a different window that was minimized the same duration.

Hit stop (to stop loading a table with 40,000 rows), toggled to a different program, option-tabbed back to Sequel Pro.

I ran a query and I think what happened was that I lost connection in the middle of fetching the data.

This occurs a couple of times and the only way I can get back to work is to close the application and in this instance this error occured

awoke laptop from sleep mode; reconnected to VPN; attempted to reactivate open session to DB over VPN

I think the connection died while I was running a query.

launching

reconnecting

stopped loading of a table

Just asked it to filter by not null on a table of 18000 records. It seemed to not be working so I hit stop.

tried to cancel a running query

tried to close the program

lost connection

Sometimes, on queries that take long (>5-10 minutes), the spinner keeps running, despite the fact that the query has completed on the server.

You can't stop the running query and have to kill the app.

It should be said that the query is being performed over a high-latency link.

internet connection lost

Hi, this program is very nice, very fast and I like, but I have a problem with this software, the problem is RUNING, every time when the RUNNING is very long time, the connection broken, thanks for all...

Accidentally loaded content of a file containing ±500MB of BLOB data

remote database, view table with hundreds of blobs. Cancelled. Crash.

trying to reconnect to server
locked up

computer came out of sleep and i tried to quit the aplication it was connecte before the sleep

I simply quit the program with Command-Q

tryed to open a table through ssh

running large query (~4000 inserts), clicked to stop queries executing in dialog window around 2500 queries through

my work computer idled for thanksgiving weekend (4 days). When I got back, I ran the following query:

update users set password=md5("poker") where email="paulmacek@gmail.com";

Using the command line:

mysql -u root -p my_database < my_sql.sql

As data is being loaded into a table, if I click on that table, sequel pro crashes.

browsing a table, moving to page 3 (of 4?)

Like...tried opening a table, or something...

some crazy network stuff - probably my fault!

closed window on broken network connection

tried to import a .5Gb sql file

I recently submit this bug, but it just happened again.

My computer was sleeping for ~24 hours, I turned it back on, ran a query, and the app crashed.

Clicked Stop on Query

Refreshed the table data

stopped a filter query

Opened the program.

sorted and it crashed

quit

filter view

Make queries for MariaDB Mysql isam tables

Tried to cancel a running query.

lost vpn connection

Had a timeout on a filter content operation (network had temporarily gone down) and this seemed to trigger the crash after about 30 seconds

changed from networks, tried to quit application on waking from sleep.

connecting to remote host

Was doing a data dump

I switched wireless network while the system was searching for a table.

Quit.

After try to view a View object on database.

I was retrieving the content of a big table (more than 200 000 lines)

Lost connection from a database and clicked on a table field

ssh was failing

select * from table... :(

Table is probably blown. Try to click on stop query and then got this error report.

I tried to access a table.

c

Executed "Show Variables"

Cancelling a long running script.

I have a table with a TEXT column, i double-click on it so the small built-in editor window appears. I press the CMD-F keys to search inside the TEXT column and a small search popup appears but it is stuck and dont want to close even if it hit CMD-W. so I hit CMD-Q to quit and the app crashes .

I stopped one running query and tried to select another tab.

tried to view Structure of information_schema.columns

Internet connection dropped out.

Nothing special

MY MAC SUCKS. PLESAS E HELP

Tried to stop a malformed query while it was being run.

nakakanakanakananaa

tried to reload connection

stopping query

Tried to load a big table!

Shutdown mac, forcing Sequel Pro to close

Loading a large table

canceled query

Retrieving table information by klicking on it in the selector while there was an insert going on

CREATE A PROCEDURE

Sorted a column, waiting on the remote database to respond, and closed the idle 1 of 2 sequel pro windows which is where it crashed.

cant cancel long running query

came back to app after a few hours idle

loaded a database

Connection was hours old, computer fresh out of sleep mode, and connected client not 'on'

Running a big query

I can't remember.

Tried to quit while a table summary was loading. There was a long-running drop table (from a connection outside Sequel Pro) locking the database at the time.

I ran a bad query. It was taking a long time and I realized my mistake (I included a "having ( count(nonexistent-column) > 1)" clause) and hit "Stop query". Then it froze and crashed.

filter

querying a big table

Opened a table. Tried to edit a value. Program froze and crashed. Connected via SSH.

canceled a query on a table.

stopped a fetch data process

fuck

stopeed the loading of a table that was taking a long time

opened sequel pro

I dropped and recreated a database with the same name outside of Sequel Pro, then I tried to access a table in that database.

it happen when run empty query immediately after program start.

I cancelled a query. Crashes every single time.

Stopped the loading of a database

QUERY WITH HIGH OFFSET

resumed from sleep, then closed the SQL Pro window, so I could re-open one and run another query.

I had lost my connection to the server by being disconnected from the network. I tried running a custom query, and then I clicked the cancel button after receiving no results for a little while.

I clicked on content

Clicked on the tab with table content for a table with all possible values of a bigint. I tried to do APPLE+q to quit.

while loading data notification was on display, I also clicked Stop without effect

Tried to view a table i think. I was doing a lot.

Was taking a while to just sort a list so i click stop and the app died.

I was shutting it down with command Q and it gave me the pop up that is quit unexpectedly.

attempted to cancel a table update

Lost internet connection while having window open to remote db

Aborted a query, then issued Command-Q before Sequel Pro came out of that mode.

reconnecting

lost internet connection, then sequel pro crashed

Just close the program.

Loading a large table

I was shutting down to restart my laptop when it failed.

quit the program while 2 queries were being stopped

reconnecting

closed a window

tried to load a federated table that was having timeout issues when contacting the server

Closed application

think I've been still connected to DB, closed Sequel Pro with cmd+q shortcut

nothing, just opened the program.

no idea. I've rebooted the computer and started the program again

Quit

Submit a delete query to delete a large number of rows, then it hung for a while even though the 'top' command reported no processing

quitting app

Try to close the window after Internet is disconnected

Executed a query on a timed out connection

Attempted to load a table via the content tab. Roughly 2.5 meg of data.

Was going to restart my mac

deleting a query.... took forever and then crashed

listing a big table

I tried to Stop a running query

masturbating

reopen

I attempted to open the Structure tab for a table that was locked by a different process (which I was running directly on the server). This caused the program to hang.

delete a million records

cancel query

cancel a job that took too long (delete a col in a very large table)
canceling was done with by click on a cancel button

stopping a browse content loading data screen

WTF is wrong with your program recently. I love it to death, but seriously, do i have to die?!

while opening a table the program staled

lost network connection while excecuting a query

Had opened two connection windows a localhost one and to a remote one with a slow connection - for the slow one I cancelled the loading task of the Content table, switched to the localhost one and tried to load another table; SP hanged, beachballing and finally it crashed.

Mac OSX 10.6.6 SP rev. 3148

selecting database

information_schema load columns

submitted a query and then clicked on column name (to sort)

ran a query

stopped a query that was taking to long

happens all the time via SSH

Tried to close a window

lost vpn connection to the remote db

I was attempting to quit the program. Did it with COMMAND + Q.

Closed the lid on the computer with sequel pro still connected. Upon waking the computer I usually can just click reconnect, but in this case sequel pro crashed.

I ran a dozen queries and exported the results to CSV files. I had cancelled a few runaway queries prior to doing the successful runs.

I clicked "stop" on a table load.

tried to stop a query

Clicked "stop" on a loading table.

stopping a query that i ran after the connection timed out

sorted a table

Just executing a query

Building an index

tried to view data in a table

quit while loading a large table

wake from sleep, tried a network operation

opened a big table, with ~ 500,000 rows

writing a query with subquery in the WHERE clause's IN statement.

SELECT * FROM table WHERE table.field IN ( [nested query] )

Waiting for going to page 1000

OS X was trying to restart after an update I believe.

I refreshed a table while my internet connection was gone.

Canceled the sorting of a very large table.

couldn't complete a sql due to a connection failure

Long request

If connection is broken while app is fetching data for table (or for that matter any request), app is consistently crashing.

clicked to close the application after already having closed the VPN to the database

I had told Sequel Pro to exit.

refreshed contents view.

retried a connection that had failed while computer was asleep.

Stopped a query, and the "stopping" alert window just hung. Tried to close the window by clicking the red x, and it just hung. Hit command-Q and the program quit.

Just executing a query

Killed connection

tried to delete 680K rows in a table.

1. Connected to server.
2. Killed access to server (disconnected VPN).
3. Tried to run query against server.
4. Clicked "Stop Query" after realizing it wasn't going to work... crash!

re connect wit and crush (ethernet change wireless)

started this query:
DELETE em3.Company, em3.Users, ematch.ematch_drupal_users
FROM em3.Company, em3.Users, ematch.ematch_drupal_users
WHERE em3.Company.ProfileOwner = em3.Users.Id
AND em3.Users.Email = ematch.ematch_drupal_users .mail
AND em3.Company.Id = 5763;

Started up, nothing came up, crashed.

Canceling a query

Tried to run a query

I ran a very big query (delete ~500,000 rows) it finished properly.
After that, I tried to count (SELECT COUNT(*) ...) the rest of the rows. It was too slow. I cancelled the query. It did not stop. I waited for some minutes. Then I closed Sequel Pro. Failed.

just opened my laptop and connected to a new wireless network from before the laptop was closed. sequel pro was connected to a mysql server through a VPN-connection which was interrupted b/c of closing my laptop.

the crash happened when i pressed cmd+w

I was browsing tables, I clicked on a table and it said that it was having connectivity problems so i clicked retry and the table came up empty (which is not correct) i then tried clicking on another table and got the spinning wheel indicating it was trying and i hit apple+Q to kill the application. It then popped up with a message saying it unexpectedly quit.

I lost connection to db because changed Internet access, and I hit retry to relog then I refreshed a table, then it crashed

imported a large database (30 MB SQL dump), sequel pro quit in the middle of importing

Connecting to a local and a remote MYSQL database.

tried opening database with over 140.000 tables....

lost my connection to the server in the middle of a query

doing a query with a large result set over a ssh tunnel with multiple hops

Cancelled loading of table content, switched to structure, then tried to load a different table. Application seemed to hand so I quit (regular, not forced). Thanks.

Trying to quit a long running query.

Sequel Pro was trying to reload content from a table. I tried to stop the reload, and then nothing happened. All the sudden the software crashed.

Running a query

stopped loading table data

closed the laptop - note completely - without switching off the system.

loaded a big table

tried to connect to a database

reconnect after sleep. pressed the "retry" connection button

select a table

Ran a subselect.

try to preview table after connection broken

Get stucked a lot of times.

Cancelling a query

clicked "stop query" while it was running

connected to mysql db running on a virtual machine (virtual box, centOS) when the virtual box network dropped

Thanks for the awesome app though! Will continue to recommend highly.

tried to quit. and then it didn't.

I refreshed a table which took really long, probably because the connection (over ssh) had timed out? When i got fed up with waiting i simply quit sequel pro since the window would not close either. That crashed the app.

stopped a query

closing a window

browsing a remote SQL db

ran query

stopped a long running query

I tried a command-Q after the program had been idle overnight, then it hung & crashed.

I lost my VPN connection, so that might be related.

clicked stop when loading a big table on the content tab was taking too long

Wireless disconnected after IP conflict. Crashed after reconnecting and trying to run query.

A large query

stopping a query seems to crash this pretty often. ;(

quitting the app

Started the application

Select

again, cancelling a long running query -> crash

changed tables

Stopped a table while loading in "browse" over ssh

Opened a connection and looked at content of table

Searching database

dasdf

opening a table from the side bar while in query-mode

stopped a running query

stopped a query

Tried to add an index to a ~9million row table. "uptime" on database server reported load usage of over 50. Had to restart mysqld.

Trying to view contents of a federated table which couldn't connect to its source. It takes forever to error, so I force-quitted.

Sorting a table with about 5000 rows over ssh, while it was sorting the table I clicked stop to cancel the sorting. Then Sequel Pro crashed

Loading data

delete a field

Run query on large table

started the app

just opend sequel pro

canceled table data loading, big table

Sequel Pro got stuck on large data set queries.

Tried to run a query

Ran a long query and hit Stop in the middle

Closed a window, I think.

clicked on a large table

Disconnected from a VPN while sequal pro was still connected to a database via the VPN.

stopped a running query

Opened and stopped viewing a large table

It was taking a long time to load a table, so I clicked Stop. It wasn't responding, so I command-quit out.

ask for a large subset of data

Tried to cancel a long query. Had to force quit to get it to end after it became unresponsive.

i was trying to stop the query and hit "stop query" 4-5 times

Large db list canclled

I refreshed a table view after moving networks. As SP was showing the throbber, I pressed Cmd+Q. SP died.

Tried shutting down my computer but it wouldn't shut down Sequel Pro (for over 30 secs) so I had to force quit. Maybe caused by the fact that I had put my computer to sleep in a connected mode but when I started it again (and tried to shut it down) the servers were unavailable.

Tried to report from a dead server...

dodgy net

Cancelled a sort-by-column operation

Opened 2 GB table
Opened the content tab
Stopped the content from loading
It crashed

I quit Sequel Pro while running a query which was taking too long.

Sorted a huge table by a column and clicked stop since I knew it would take a long time. Seems like it doesn't like stopping big sql sorting scripts in the middle of them.

changed a query

stop a table from sorting

Mac battery power perished. Upon attaching power and rebooting mac, Sequal Pro crashed,

aborted a badly written query that took too long

I had imported a .sql file that contained a very large table (~3M rows). I tried to cancel the import when I got tired of waiting for it to finish. I had to force SP to quit using "Force Quit".

running big ass query over vpn, late at night

stopped filter

Quit with query running

ran a query that took several seconds to complete

launching the program

i don't remember!

I opened it x_X

connected to a table and it hung

Quit

Hi,

It appears that the keep connection alive is not working, my internet connection here will close down connections pretty quickly, unless the server is pinged on a regular basis. It looks like you've included this option in the preferences, but it's not working properly. I'm sure the logs will tell you more than I can. If you need help testing let me know, I'm happy to help.

Mike

trying to quit while a query was stuck

Stopped an insert query that was taking too long

Editing a field in a remote database.

I then used Cmd + W to close the window in order to disconnect from the database, the spinner appeared and then Sequel Pro crashed.

ran a query, lost internet connection, then tried to stop the query. sequel pro hung and crashed.

Canceled a query

importing + browsing a table

A larger nested query. I did expect the shutdown, though. I ordered it, after all. I didn't like that the query took forever and that i was unable to cancel it so I quit the application and am restarting it now.

closed the window

command-w

???

i was trying to stop a query that took too long (a bad like %%)

Executed 2 queries on 1 line.

cancelled a multi line insert (using selects) into a table

Cancel loading the contents of a very big tables over ssh.

tried to show content on a table with a lot of BLOBs in it. Is there a way to limit by default the number of rows brought back, or to not bring back binary data?

woke from sleep, tried to run a query

crash after network disconnection

1. SequelPro was connected to a database on a virtual machine
2. Shut down the virtual machine
3. Tried closing out SequelPro by hitting the "x" button (top left corner)

At the time, I also had another window of SequelPro open that was connected to a different database on a different server.

Pressed Command+W

Seem to have a temporary problem with the database which caused Sequel Pro to hang and quit.

MySQL error while making a backup here just in case it helps;
mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `articles` at row: 12

Ran a query but at the same time the server crashed

lost connection to internet

Opened the program, nothing else.

Canceled a query, a simple join....

kill a long running query

stopped a querry

lost connection

Closing connection

stopped a running query

trying to access a database

tried to access a table while it was being imported

comcast internet dropped (at the box) while doing a table lookup, connection never timed out, and had to quit app. Instead of quitting gracefully, it crashed.

hung upon staled mysql db connection.

i just executed a simple query (select * from where ... is null).

i tryed to run a 100000 result query and then i clic on stop query, it freeses and then crashes

I tried to open a connection to a database

flaky connection

Disconnected my internet connection.

I quit Sequel Pro while waiting it to load a locked table.

Opened the program.

I tried to close it.

Trying to drop the database.

Clicked "Cancel Query" on a query that was returning a column value for every row in a 360,000+ row table.

Tried stopping a long running query but it never stopped.

It had been idle for several hours when I was not at computer. I returned to computer, had sent an email message and then clicked on icon in dock to return to Sequel Pro

always crash!

tried to open the software

always crash

I closed the window by clicking the red bubbled x on the top left while being connected to a remote MySQL database over a SSH tunnel.

(PS Thanks for making Sequel Pro!)

select on 60000 row table

!) Open a connection to a database
2) Put your computer to sleep
3) Unplug network
4) Wake the computer
5) SQP is likely to crash, or show an endless stream of reconnect dialogs, which prevent copy-pasting Query editor contents to safety and/or saving the session

Opened the content of a large table

No clue.

I killed sequel pro while a query was being executed

Running a query

tried to open a table that was having data imported into it from the command line.

choose a database

can't remember

Shut down

trying to load dbs

On the command line, import a huge data set into an innodb table. Whilst partial complete, use sequel pro to go to that table, either the content or table info tab (can't remember). Sequelpro says it's loading the table, but I gave up after 5 or 10 minutes, as it didn't finish. I pressed cmd+q, and *bang*

lost internet connection

just quit sequel pro

i launched the program

it quit

ran a query, hit stop, then crash
- query was a group by with one inner join and a having clause

Cancel a table look up by pressing the "Stop button"

Running a query

cancelled a query

Crashes all the time for everyone you guys know this right?

When network connection goes off - hard to reinstate the application

stopped the loading procedure of records

put machine on standby, reconnection to DB failed

canceled a query

i quit the program while a query was canceling

clicked stop query and it broke

clicked on stop query

stopped query

- two connection with local db server (makes total 3)
- one with query browser open
- connection over ssh
- trying to load table for remote db connection with ssh
- crashes are frequent (I guess something to do with connection breaking in-between)

Stopped a SQL query that had been running too long - I think the server had reached the maximum connections

Tried to connect to a remote database

Tried to access a table (I believe) is being dumped into (mysql -u -p < dumpfile.sql).

de

Pressed refresh while application was shutting down.

quit sequel pro by accident

Shut down mac without closing application.

Selected another table to view

1. Attempted to Export - MYSQL Dump ... with 2 of 13 tables selected
2. Export seems to have worked, but Sequel Pro hung with export dialog open
3. Had to force-quit to exit the program because it would not quit normally
4. I frequently have problems with dialog (status/cancel) windows not closing which result in a hung window. Usually, I can open a new window and then quit normally, but not this time.

closed a window after waking from sleep

Tried to open from Desktop icon

Sorted a filtered list

window to a server was open. Server's on a VPN. I reconnected the VPN, then submitted a query in the window. The "wait" dialog with stop query button appeared. I pressed that after a few seconds and then Sequel Pro crashed.

sometimes it gets in a state where it doesn't crash, but I have to restart the app to get it to connect.

Even so, this app is best of breed for me and I really appreciate all your hard work.

This seems to be a reconnection problem. When I change locations or drop VPN, it can't seem to reconnect properly and stalls out.

Canceling a long running query caused the program to hang. Waiting 20 mins for the query to cancel didn't seem to help.

a query after I awoke my macbooks pro

Execute a query and stop it

Slow connection, pressed stop to stop loading a table

Connected to a database that was in the process of being restored, then tried to view the table that was currently being restored, and decided to quit application before the table view had returned.

opened table view for a large table which was still importing data from terminal. 1 million + records

wifi sleep wake up and use aircard

I was using it

read table from DB over a slow Inet connection

deleting an index

Had stopped a process and that's when it crashed.

trying to bring back / resume the Sequel Pro from a staled 3G connection, it will stuck in the loading state.

Close a Sequel Windows

killed the server opps

Stale connection to remote server, attempted to run a query (which took a long time). I cancelled the query and then the application crashed.

computer was in standby and still connected to sequalpro..I woke up laptop and tried to connect after esblishing network connection..it hung so I killed the ap.

just crashed, maybe unavailable connection because of close and reopen of laptop. Love the app though!

tried to run a query and was stuck

executing a very large query (700mb)

Put my laptop to sleep last night. Came back and tried to reload a table. I knew the connection had been broken. It died.

Closed the app

Just starting up

lost internet connectivity whilst loading remote table

stopped a query after the laptop was disconnected from the network

stopped executing query

Trying to sort a 192 GB table (which was still growing). Essentially, the connection just hung, so I quit in the middle of it.

reconnecting with a database after sleep.

stopped a long-running query

just opened it

reconnected after waking from sleep

Sort phpBB table

Lousy connection...

tried to pull out of hung mysqld

Launching

switched to this app after a while

delete all from large table, click top and quit app

selected data from a table

running query over ssl (connection may have dropped)

lost network connection

Stopped a long long script

opened db that had inserts running

Stopped a long running query

Cancelled a query

Close programm

I stopped a query that was running a different database than the one I was actually watching using dbname.tablename

aborted query with a lot of output

executed a (probably stupid) query

Opened multiple windows with different databases.

Tried to cancel a query

Trying to execute a query

Selected a table to view.

Tried to sort table

quit the application during a running query.

just started the app

Shutdown computer without quit Sequel

I'm using Mac OS X, so closed the laptop without shutting down the whole system. :)

Do you guys even look at these?
Just running a normal query, nothing special.
Crashes constantly...hopefully 1.0 will be more stable!

beachballed all on itself

quit the software

annidate queries

clicking the "stop" button on the "table loading" popup

stopped sorting a 'bigger' table

closing a processlist window

tried to close the window

Not sure. Are you guys still developing this ? It's a great tool

stopped a table from fully loading

sorting a table with 15mm rows, then cancelling, then sorting again while the original sorting progress window was up

Hit cmd-Q

cancelled a running query, because my internet connection was shaky

tried to resort a query by a click on the column header. It was probably because it was the first time it was ran since hibernation.

I quit the application while it was trying to load table info for a database on a remote server.

had a stuck query running, didn't try to stop it (because that didn't seem to work last time)

trying to connect to db that timed out

tried to stop a loooong query

well, just closing the application window with cmd+w :D

I was editing the DB, accidentally closed the WiFi connection, sequel died.
(i do this, very very often)

BTW, nice software, thank you guys

Loaded a big table content and hit "stop"

Running a query

Just opening a table with the Content view, nothing special

cancel query when internet connection was down

Opened the application

Running a query on a huge table with no indices. Lots of string comparisons too. Yeah, I'm awesome.

stopped a query

put computer to a sleep, program didn't answer after that for a while so I forced it to quit.

Ran a stupidly huge query that would take *HOURS* to complete.

What would be nice? To have an option to run a query in the background, so I can get on with my job. I'll buy you beers if that can happen.

query a table when the connection was slow

Woke up computer from sleep and VPN conncetion to DB had dropped

table got locked by external program, tried to access the table from within sequel pro.

stop button to cancel had no effect, using quit menu item crashed sequel pro

long running query was in progress

Quit

stopped a query

connection lost

tried to cancel a query (mysql connection of ssh tunnel)

tried to cancel a running SELECT query (connection over a ssh tunnel)

Seems to be when i had a disconnection from a databases which was connected trough ssh-tunneling.

-- attempted to load a table from a database in an open window that had been left on overnight (through sleep)

Seemed stuck - so force-quit

I got disconnect from network, so just ran the query and then connect back to network.

1. Filtered the content of a table.
2. Put Mac to sleep.
3. Wake up Mac.
4. Refresh filtered table.
RESULT: Crash.

Note: this was a remote connection, no SSH.

Was opening a mysql connection to a db and then closed Sequel Pro before the db connection had been completely opened.

Stopped a sort column on content.

cancelled a query

stopped a simple query that was spinning endlessly

Waked from sleep and closed the program

searching db

Tried to run a query with UTF-8 single quotes (different right and left quote characters). I cut and pasted the query from the web and forgot to change them into standard ' single quotes. Thanks - it's a great tool!

just closed sequel pro after coming out of suspension

I was deleting a database that has a lot of stuff. The program stopped after I click ok when it asked me to make sure that im going to delete this data base

cancelled a query

After opening my laptop and waking it from sleep mode, I saw the message that I was disconnected from the remote server which I was connected to through Sequel Pro. This is the expected behavior. Without clicking okay or cancel or whatever the buttons are on the alert message, I used CMD+W to close the disconnected remote connection window. That action triggered the crash. When are you guys going to add support for PostgreSQL? That's probably a different ticket.

I was loading a database that was growing.

closing a connection

Locked up running a query... had to kill it. This happens a LOT for me on queries that take a long time to run.

canceling a non-indexed sort of a remote mysql database. This happens all the time >:(

tried to stop a query

I have displayed table data

Ran a custom query with a spelling error, stopped the query and tried running the fixed query again.

trying to search table and it froze

no idea..

tried to open a table for viewing/editing

tried opening a table

Pressed command+q

cancelled query and it crashed

stop

I was trying to stop the load of data
It was taking too long and i just needed few elements

ran a select query

I was doing a long transaction against one server (add a compound index against 6mil rows). In another window run a query that takes a while, and hit "Stop Query". That's when the shit hit the fan.

Running a difficult and big query

performing a query after a long idle period

Stopped sorting a table midway.

close an existing connection to a DB after switching to a new wireless network

closing a window after the connection (via ssh tunnel) had ended because laptop was closed and reopened (other windows showed disconnected dialog, this one didn't).

viewed a table

delete foreign key w/ indexes

Run a query with a commented query with # above the valid query to run.

launched queries, it kept running apparently without updating the running process name, clicked on "cancel", it hanged then crashed

Tried to open a table from a database

I put the computer to sleep and unplugged some external monitors (using the DisplayLink USB driver). When I woke the computer up, the computer thought the laptop screen was 0x0 pixels or something, and a couple programs crashed. I had to plug in a display for Mac OS X to reconfigure and work okay again.

Tried to edit a table

tried to stop a query

stopped loading a table

Only browsing

Executed a long query. It had finished running on the server but the display still showed "executing query..." for a long time.

i clicked table after 20 hours from last use.

Lost internet connection, didn't realise and tried to re-order column view. Table refresh froze. Force quit.

Long query, cancelled the query, then CMD+Q Sequel Pro

Great product, keep it up!

Cheers,
Ricardo

I quickly shut a connection with CMD + W and instantly tried to open a new window with CMD + N before the old even hided

tried running a query ?

Searched a database. Never got the results back.

Selected a database table while data was being imported to it

I HATE APPLE®

Tried to quit the app (three windows open, connected to Mysql running in Centos VM running in VMWare

was sorting table and tried to cancel query

running a query

a query

click stop in progress overlay on default load of table content. probably 2000 rows loading, crashed after clicking stop right at start of table load

tried to stop a long running query that I realized was going to take hours and return billions of rows due to a bad where clause.

I tried to close the front window. I had 3 other windows open behind it, all connected to the same server as the front window. Then it crashed.

Click stop on a query that i just started executing.

Starting the app

crash when starting

tried to sort a table

clicked "stop" while loading a large table

cancelled a query that was hung.

Tried to cancel query that was running against a server that had been disconnected

I was switching from one Database to another and the program froze

My internet connection dropped. After that, I had some trouble getting the Sequel Pro dialogs to respond. I had multiple windows/connections open.

not sure

Just trying to use it ...

cancelled a query

I had been VPN'd into a server in order to connect to the database, and I quit my Cisco AnyConnect VPN Client before attempting to close Sequel Pro immediately after.

I had been VPN'd into a server in order to connect to the database, and I quit my Cisco AnyConnect VPN Client before attempting to close Sequel Pro immediately after.

switch DBs

Nothing.

connecting to remot db

Try to reconnect ... jammed, then close the connection.

executing a query

Refresh remote SQL (it has been going on for 10 hours) I was working on other DBs. The computer could not goto sleep. Fan started running. In the morning I Force Quit.

sometimes Sequel Pro crashes when it tries to reconnect to a db server I access over a Cisco VPN after being left idle for a while.

Running a query! :)

LEFT JOIN Query on 2 tables...

I switched between the tables with content view and I got progress dialog 'Loading my_table_name', which stayed there forever. I did not find any other way to get rid of it, other than to close the whole Sequel Pro (I used normally Quit from menu).

i'd just reopened the 13" MBP and clicked on structure - said connection lost - tried Retry instead of Reconnect. Fall over occured at this point

closed a window. looking forward to new version

laptop went to hibernation after battery ran out.

just clicked stop on a long running select that I realized I needed to filter more

Tried to stop a query in flight with that stop button you have on the pop up. You'd think by now I'd know that was futile.

loading a remote table

just opening the program

ran a query

Was just quitting the app

trying to load a table

Trying to close the application

stuck trying to reload a record list; tried closing connection window (wouldn't close) so did Quit via dock; eventually crashed.

ran show processes. server might have been dead though...

Tried to stop display of Content for a table that was still being loaded.

quit the application

tried to close an open connection window using cmd-W

lost my internet connection

I have a database with tables with over 2 gigs worth of data. This app seems to simply crash when it tries to export or import. It sits there idle without any feedback, spinner or progress bar simply sits there not showing if the export has finished. The program simply crashes after that. Force quit sometimes is the only way to exit... I had to revert back to phpMyAdmin

Disconnect from an idle database

browsing remote large (wide) tables

I plugged in a network cable and turned off airport. Sequel Pro was connected to a server over the wifi network interface and the next time a query was attempted it crashed instead of the expected connectino dropped or reconnect kind of message.

trying to load data from a federated table, clicked stop but stop did not happen...

tried to open a table after not using the program for a few hours.

opened view >1000

My VPN crapped out & I reconnected

Huge query

quit Sequel Pro

i ran a query....previously had run a similar one with no problem. didn't expect it to crahs

your mother

accessing repaired table.
previous repair success unknown because it hung up during repair, had to force quit.

Quit Sequel Pro

cancelled a query

Quitting after letting the application sit overnight with the computer asleep and active connections open.

stopped a query running on a remote server (ie. one that I was connected to via ssh)

Cancelled adding an index to a large table.

Tried to stop query.

lost wifi connection

I was two update statements on two different database servers. The updates had been running for a while.

Closed current connection window

Put the Mac to sleep and woke it up on a different wireless network, then hit Cmd-Q before Sequel Pro realized it had lost the connection.

cancelled loading a table with very big column values (taking a long time to load)

Refresh?

Executed a query after the computer went to sleep and was woken again. The connection had been lost and the query stalled. I clicked cancel and it crashed.

Sequel Pro seems to need to 'quit' after the computer returns from a nap, as it is unresponsive. Not a big deal, great product otherwise!

crapped out while quitting *shrug*

Launching a long requests hangs the thing.
Even stopping keeps it hung.
Have to force quit, which closes all my sessions....

It was trying to open a table. And was just infinitely hanging with the wait indicator spinning. I selected Sequel Pro -> Quit Sequel Pro and it crashed.

clicked on a table

another long request I just wanted to cancel. If cancel doesn't work, don't enable it ;)

shutdown the vm running the database

tried to run a query

switch to a different database

Lost network briefly. This usually locks up Sequel Pro.

Stopped an operation

Stop fetch content of table

loaded 900 MB SQL file

A very large query

Closed sqlpro after going to standby then going somewhere else. Hung for a minute before crashing; was probably trying to get connections back?

Nothing - just opened the app!

Nothing

Did a text filter ("is") on a small-medium sized table

I cancelled a long query

DOn'y know the reason

clicked on a table on the left column then a "loading" box popped out.
i waited for about a minute then close the application.

the current view was the "query". feel free to contact me if you need more info!

network connection went out (mysql connection over ssh)

sorting the table in the content viewer using a non-indexed column made it crash

standyby mode .. after resume no network connection

I was cancelling a query.

Attempting to quit the program. I think it was hanging prior to my attempted quit.

I was viewing a database, then I deleted it via mysql CLI, then I switched to view another database and it was spinning and loading for a long time, then I hit command Q and then it died.

Attempting to load table data on a remote database. My network connection had briefly been disrupted while switching from wired to wireless mode.

Quit the process during a long query

loaded large table over SSH, tried stopping the query as it was spinning

reinstalled mysql

aborted long running query

attempted to load a table while in Relations view

sleep the laptop overnight.

i was opening a table which took forever to load, tried to stop/quit and it crashed.

just running queries.

App said that the connection had timed out, and asked me what to do. I selected "Retry", and the query re-ran. Then I hit the "Stop query" button and the app crashed.

Tried to stop a rather long SQL query.

Not sure.

Reloaded a table then pressed command + Q

disconnected from the network

Automatically reopened: new report received from a revision after this problem was believed to be fixed.

trying to export a large database table

Tried to export a db that I have exported several times before successfully.

tried to browse a table.

exporting data from remote db server

Opened the application

export a innodb table as csv (mysql 4.1)

i was just trying to export a table as a csv file

Exported a table (300 records, 25 columns) to a CSV file from the option-click menu under favorites.