MySQL Bugs: #72357: Crash-prone Routine Groups.

Bug #72357	Crash-prone Routine Groups.
Submitted:	16 Apr 2014 13:22	Modified:	26 Aug 2014 18:14
Reporter:	Chris Brown	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	6.1.4	OS:	Windows (7 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	routine groups

Description:
Since I updated from 6.0.4 to 6.1.4, EER modelling is crashing painfully regularly, each time losing the piece of work I was last working on - meaning I have to route around to try to backups find whatever's lost.  In the past hour it's crashed over 10 times.  Needless to say I'm close to throwing my laptop out the window.

Usually it doesn't show an error, but once it has returned an error and did NOT crash (which makes me think it's probably 2 separate bugs?):
"Object reference not set to an instance of an object"
Fixing that, however, probably won't fix the problem, given that it actually didn't crash that one-off time.
At the time I was clicking out of a Routine Group after editing its contents.

This is the same behaviour that causes the general crashes.  No specific action seems to cause them, they're fairly sporadic - but it happens a lot when I'm editing routine groups and doing all the motions involved in moving procedures between routine groups (copying, clicking out the routine group, double clicking another routine group, pasting, saving).
It should be noted that since it crashes pretty much guaranteed every 10 minutes, I save very regularly (after each copy & paste) so it could potentially be a bug in the saving of a model, given the increased frequency of the saving.

How to repeat:
I can't recreate this with consistent step-by-step actions.

It looks like the the quoted error provided is something to do with editing the routine group name.  I had a situation a minute ago where I got the "report bug" popup each time I typed another letter in a routine group name.
Looks like a different bug entirely.

Please provide the model file. Thanks.

Added file.  The routine groups are at the bottom.  After I wrote the bug report it actually stopped happening, so it might only occur after long use (although I don't see how, given it closes each time as it crashes).
You may be able to replicate it if you mess around with the routine groups at the bottom - copying things between them, moving them around, renaming them, etc.

I have the same problem. It happens when I add a view to one of my models. If I remove that particular view, it syncs the database. But as soon as I add a view, it crashes, with no error message.

I tried with short and long view names, with the simplest DDL (such as SELECT NOW()), to no avail.

This started occurring once I upgraded to 6.1.4. 

Currently I have 21 Diagrams in one modal file.

I'm planning to downgrade.

Perhaps we should update the Severity to critical? It's not letting me sync the model with the database.

I downgraded to version 6.0.9 (the one I had before the upgrade). Problem was resolved. So behavior is broken in 6.1.4.

Good to hear this isn't all just in my head..
I'll update it to S2 severity, since it seems to have greatly hindered your use.  I originally flagged it as non-critical because for me it was very unpredictable - only seems to happen on long sessions using models for me (maybe it happens sooner for you because your model is more complex).

@Sherzod Ruzmetov are you able to provide the model file which that offended view?. Thanks.

Worth noting that my problem may have been down to a corrupt atl.dll file in windows.  I have not had any problems since running a sfc /scannow (which fixed a lot of sporadic behaviour in other programs too).  Sherzod's problem may be different, though - so it may be worth pursuing that separately.
I will update this bug report if the problem re-occurs, but I don't image it will now.

I'll close this as Can't Repeat as the original reporter says it was a problem in their local machine.
Sherzod, if you still see the problem, please file a new bug and include your model file in it.