Sequal not responding when running a query

[Rodrick Borg]

Sequal Pro becomes unresponsive when running any queries , even simple queries on a local instance .  The RAM usage spikes to about 6GB . Any help ?

[Rowan Beentje]

Hi Rodrick,

Any chance there’s some enormous queries (big data imports) in your query history? We just use a .plist for these so it doesn’t cope very well with extremely large blocks of text, and that would get modified whenever you run a new query, however tiny…

Rowan

> On 27 Jan 2016, at 09:43, Rodrick Borg <borgr...@gmail.com> wrote:
>
> Sequal Pro becomes unresponsive when running any queries , even simple queries on a local instance . The RAM usage spikes to about 6GB . Any help ?
>
>

> --
> You received this message because you are subscribed to the Google Groups "Sequel Pro" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sequel-pro+...@googlegroups.com.
> To post to this group, send email to seque...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sequel-pro.
> For more options, visit https://groups.google.com/d/optout.

[Rodrick Borg]

No , even running a very basic query with limit 1 will result in this . running the same kind of query will take 0.02 seconds in mysql workbench .

[Rowan Beentje]

Hi Rodrick,

I appreciate that running a small query *now* results in this, but have you run very big queries in the past? These get stored in the query history (see the “Query History” dropdown just below the text editor area). The way they’re stored is rather basic, because we’re not expecting people to run enormous queries there, and so if there’s something big in there then even running a tiny query like “SELECT 1” will cause high CPU and RAM usage as it tries to update the history.

You can go to the “Query History” dropdown and choose “Clear Global History” to see if that helps.

If not, is any useful output shown in Console.app? Does a guest user account show the same problems?

Rowan

[Rodrick Borg]

Hi Rowan

Thanks a lot for your help . Clearing global history solves the problem .

Regards
Rodrick