Bug #52382 'Failed Assertion' shared_ptr.hpp
Submitted: 26 Mar 2010 1:22 Modified: 1 May 2010 6:55
Reporter: Jeff Cariveau Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.16 oss beta OS:Windows (Windows 7 Pro x64)
Assigned to: Assigned Account CPU Architecture:Any
Tags: crash, Failed Assertion, shared_ptr.hpp, synchronization error

[26 Mar 2010 1:22] Jeff Cariveau
Description:
I am currently testing your Workbench and building a new database structure concurrently, and ran into a problem after re-arranging two tables into three.

System info:
MySQL Workbench OSS for Windows version 5.2.16
Cairo Version: 1.8.8
Rendering Mode: OpenGL requested (create a diagram to confirm)
OpenGL Driver Version: 2.1.8787
OS: Microsoft Windows 7  (build 7600), 64-bit
CPU: 4x AMD Athlon(tm) II X4 620 Processor, 1.5 GiB RAM
Video adapter info:
Adapter type: 
Chip Type: ATI display adapter (0x9710)
BIOS String: BK-ATI VER010.094.001.007.000000
Video Memory: 524288 KB

Everything worked fine, until I went to re-sync the database to the newer model, and on trying to gather the old structure, it crashes every time.

http://img36.imageshack.us/img36/5195/pagecrash.png

http://img171.imageshack.us/img171/5357/ccrash.png

I can provide the actual structures on request

How to repeat:
I can provide the data in question (blank table structure dump and the modeler file) and even visual studio 9 logs
[26 Mar 2010 12:23] Susanne Ebrecht
Please provide the mwb file.
[26 Mar 2010 15:23] Jeff Cariveau
http://www.bigds-services.com/bds.mwb
[1 Apr 2010 6:55] Susanne Ebrecht
I get 404 error here.

Please upload your mwb file either here at our bugs database or at our ftp server.
[5 Apr 2010 18:16] Jeff Cariveau
this is the file causeing the update <> sync error

Attachment: bds.mwb (application/x-zip-compressed, text), 58.45 KiB.

[1 May 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".