Is the Sequel Pro project dead?

[Steve Williams]

I have been experiencing a number of crashes since upgrading to Yosemite several months ago.  I was hoping to find a new release that would address these issues, but it looks like there have been no releases since Jan 2013. 

Is this project still alive?  

I hope so because it has been the best replacement for SQLYog since I switched to Mac.  

Anyone else experiencing random crashes?  For me it happens randomly when I switch to viewing another table.  Sometimes hours can go by, other times only a few minutes.  

Thanks!

Steve

[Jakob Egger]

Hi,

I've recently seen Sequel Pro crash too. Looking at the crash log, it seems similar to an issue I've been experiencing with my own app, PG Commander.

It looks like the app crashes when a view tries to access a delegate, but the delegate has been released already.  Usually the delegate is either a window controller or a view controller, and this shouldn't happen because the view shouldn't live longer than the view controller.

However, in OS X 10.10.1 something seems to retain some views for some time even after view/window controllers release them. I have no clue why this is happening, and I believe this is a bug in OS X.

Unfortunately customers don't care whose fault it is that an application crashes, so I had to use a workaround in PG Commander. Every time a view controller is deallocated, it sets the delegate & datasource of all views that refer it to nil. Additionally, the target of segmented controls caused problems, so I also set them to nil.

In one of my view controllers I use the following to work around the issue:

-(void)dealloc {

[self removeFromSubviews:self.view];

}

-(void)removeFromSubviews:(NSView*)view {

for (id subview in view.subviews) {

if ([subview respondsToSelector:@selector(delegate)] && [subview performSelector:@selector(delegate)]==self) {

[subview performSelector:@selector(setDelegate:) withObject:nil];

}

if ([subview respondsToSelector:@selector(dataSource)] && [subview performSelector:@selector(dataSource)]==self) {

[subview performSelector:@selector(setDataSource:) withObject:nil];

}

if ([subview respondsToSelector:@selector(target)] && [subview performSelector:@selector(target)]==self) {

[subview performSelector:@selector(setTarget:) withObject:nil];

}

[self removeFromSubviews:subview];

}

}

This fixed the crashes in my case (obviously it doesn't fix the memory leaks), so adding this to every view controller / window controller might help.

Maybe adding something like this to every view controller / window controller in Sequel Pro would help?

Best regards,

Jakob Egger

--
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 http://groups.google.com/group/sequel-pro.
For more options, visit https://groups.google.com/d/optout.

[phong]

Yes I am experiencing crashes after upgrading to Yosemite, most frequently when saving from the Database > User Accounts... window. Most of the time when exiting that window, it crashes. And when I send the crash report, it says it cannot be sent.

I really like Sequel Pro, and I hope this is fixed.

[Makoto Hara]

Hello, I'm a contributor for translation of Sequel Pro.

Our project is still alive.

See latest updates at http://nightly.sequelpro.com

Let's try latest build if it still crushes or not.

As Steve told, it has passed long time since last release.

I think that significant difficulty is caused by PostgreSQL support.

Because there are many MySQL specific features exist even in locale texts.

How about separating project into MySQL and PostgreSQL?

Please give me your opinion about Postgres support.

Let's contribute to our project anyway.

Sequel Pro is the best MySQL client.

Thank you,

Makoto Hara

[TheDO]

Just curious if there's an update coming for Yosemite compatibility? This doesn't need to wait for new features or other bug fixes, but merely UI fixes.

One example is button focus rings. They don't seem to appear. Pressing the Tab key to move to the next button does move the focus, but without any visual indication. It's these UI bugs that could easily be fixed in their own release, no?

[TheDO]

Just to reply to myself... I see that the latest Nightly does indeed fix the Yosemite UI bugs that I've been noticing. That's good. :)