Menu

#18 1.2 Crashing behaviour in diagram editor

closed-fixed
nobody
9
2007-05-14
2007-01-03
gmckone
No

After importing a database from SQLServer, and modifying the tables and their relationships, and after saving the work in the XML format, I have experienced crashing behaviour.

Normally this has occurred when I have deleted an object, and have received a Memory access error.

In one case two tables were related Table A contains FK to TableB's PK Deleting one of the tables caused the crash.

In another case a relationship between two tables 1-N identifying was deleted and caused the application to crash.

Stabilizing this application would be very much appreciated.

I can't repeat the error, but have witnessed it at least 3 times in less than 2 hours of use.

Blessings.
Greg.

Discussion

  • gmckone

    gmckone - 2007-01-03

    Screenshot of memory error caused by deleting an unrelated table.

     
  • gmckone

    gmckone - 2007-01-03

    Logged In: YES
    user_id=1119014
    Originator: YES

    Had this occur just now with deleting a table that had no relations. (19 minutes of program use on Windowsxp)

    See screenshot, this is the first of (100?) many error windows that pop up over and over.
    File Added: dbdesignercrashing.GIF

     
  • gmckone

    gmckone - 2007-01-03
    • priority: 5 --> 7
     
  • gmckone

    gmckone - 2007-01-06

    Logged In: YES
    user_id=1119014
    Originator: YES

    OK I've found a way to dramatically increase the probability of receiving a memory access error like above. If they are related and the following example can be addressed, then this may be the clue that solves the above issue as well. (if it isn't exactly the same). If you have a chain of tables that are related Certifications -> Training -> Operators and you open the middle table for editing (training), and while that is open, you delete one of the relationships to that table. (yes I'm sure I want to delete the relationship I just chose to delete)... and then try to save the table changes, you will likely experience memory errors. Try recreating the relationship and you will likely experience memory errors. (Pick the most complicated chain of tables you can find to boost your chances).

    I hope that helps the developers fix this issue of stability. I'm going to reload from backup and redo whatever it is I've done in the past few minutes.

    Blessings on you.
    Greg.

     
  • Joao Paulo Schwarz Schuler

    Logged In: YES
    user_id=187362
    Originator: NO

    I have just reproduced the problem about "and while that is open, you
    delete one of the relationships to that table".

     
  • Joao Paulo Schwarz Schuler

    • priority: 7 --> 9
     
  • Joao Paulo Schwarz Schuler

    Logged In: YES
    user_id=187362
    Originator: NO

    About the problem: "and while that is open, you delete one of the relationships to that table".

    Solution: EditorTableForm and EditorRelationForm are now modal. So, this particular BUG has been fixed. Other problems may appear in another places.

    This FIX is going to appear in the next version (1.4).

     
  • Joao Paulo Schwarz Schuler

    • status: open --> open-fixed
     
  • Joao Paulo Schwarz Schuler

    • status: open-fixed --> closed-fixed
     

Log in to post a comment.

Auth0 Logo