dreamweaver cc 2015 crashing when accessing my mySQLi panel

Hi,

Dreamweaver CC 2015 Build 7851 crashes - closes down with a report to Apple - on a frequent basis when I access the server behaviors panel as follows:

Server Behaviors > + > WebAssist > MySQLi > MySQLI Recordset

Sometime I can use the panel 3/4/5 times without issue and other times its almost every 2nd time I try to add a new recordset or modify an existing recordset. There is never an issue the first time I use the MySQLi extension after DW starts or restarts after a crash.

Its getting very tiresome keep restarting DW!

If it's any help, I can send you an Apple report next time it happens?

Any help gratefully received.

Regards,

Mike

This usually happens due to an inconsistent FTP connection. It is probably failing while uploading the files it needs to check the database for the table and column lists.

Are you using a remote server as your testing server? You may want to consider using a local testing server if this continues to happen. I'll do some more testing on that DW version and OS, but the dump wouldn't mean anything to me.

Hi Ray,

We have checked our LAN system and can find no issues with timing. I have noticed today that I can only create one MySQLi recordset then, if I try to create another, Dreamweaver crashes out every time. It seems to happen more when creating a recordset then anything else if that's any help?

Cheers,

Mike.

If you post a US phone number or Skype contact information I can give you a call and try debugging it with you in a screen sharing session over the phone.

Hi,

I am getting the same issue. I have switched from using Windows to a Mac and have the latest build (Dw 2015, build 7884).

The Windows version doesn't do this, however my issue is pretty much the same as Mike's...I can use it a few times and then all of a sudden the app just quits and I get the OSX report coming up and asking me to Reopen Dw.

I logged in yesterday to make sure that I have the latest version of MySQLi and I have.

Did you manage to fix this for Mike?

Cheers
Nick

PS: If you want the log that OSX throws up let me know.

Hi Nick,

I regret not.

Ray has offered to help out by using Skype to see the problem but we have not had the time to go down that route yet.

We did load the Mac Pro up with 32Gb of ram (was 8Gb) which seems to have helped a little in our case, although it's difficult to tell, but the error seems to be a little less frequent. We have also adopted a policy of making a "Save All" before going back into the Server Behaviors panel. Again we are not sure if this helping the issue or not.

I am sure it is a Mac issue as I have not seen anything posted by Windows users. We did consider buying a Windows machine to use for development but that somewhat defeats the object! ;-) It would be interesting to hear from other Mac users who don't suffer the problem and see what OSX, testing server machine, server software, and Dreamweaver versions they are using - perhaps everyone develops on a Windows machine and it's only you and I on Mac's! (ha ha)

Ray:
I will be in contact shortly regarding a Skype session with you. Sorry, but just a little busy at present. Thanks.

Cheers all,

Mike.

Hi Mike,

I don't think it's your Mac setup that is the problem. We're doing the "save" before going into the Server Behaviors which means we're not losing too much work. It's just causing a time headache which isn't great when at the end of the day that's what we sell.

We have Parallels running on our Macs with Windows 10. This means we have a Windows environment on each Mac however we want to develop full-time in a Mac environment hence switching over.

Hey, if we're the only ones on Mac's then there are only two people in the world that are decent!! ;-) lol

Cheers
Nick

Mike & Nick,

This seems to be a persistent mac issue, I run a Late 2015 5K iMac with 32Gb Ram and I run into this issue as well. It seems to me that Dreamweaver on the Mac has a memory leak issue particularly when using Server Behaviours, this is certainly the case with CS6 and it would seem that it has not been completely solved even in the latest version.

I run a local server via MAMP that I do all my development in and it still happens regularly to me. Like both of you command + s has become my default after making any changes.

Now there are at least 3 decent people in the world !

Regards,

Dave Buchholz
I-CRE8 Limited

Hi all

Dave, I think you could be right with the memory leak. However I've run other extensions without the app crashing so it could be on both sides.

Ray, if we were to send you the report after the crash would that help you debug? Unlike Dave I'm running the latest version of XAMPP so it looks unrelated to localhost unless its Dw Server Behaviors having a fit when it tries to open connections.

Thanks
Nick

Those crash reports are useless to me... only Adobe could debug with them and they haven't given us any advice on them.

I think it is a memory leak related to larger UI's. Other extensions probably don't have as many screens and options. We are looking at options for shrinking our memory usage to prevent the leaks from having effect on our interfaces. Right now we really only see it in the large DataBridge and SecurityAssist UI's, which supports the memory leak theory.