| Bug #63678 | Crashed while adjusting a table size (in EER diagram) | ||
|---|---|---|---|
| Submitted: | 8 Dec 2011 18:26 | Modified: | 12 Jan 2012 16:10 |
| Reporter: | Javier Domingo | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench: Modeling | Severity: | S1 (Critical) |
| Version: | 5.2.36 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | crash | ||
[8 Dec 2011 18:26]
Javier Domingo
[8 Dec 2011 19:14]
Valeriy Kravchuk
Please, check if this ever happens with a newer version, 5.2.36.
[10 Dec 2011 12:39]
Javier Domingo
Confirmed, it also crashes. Steps to reproduce: in a EER Diagram, modify in a medium size db (15 tables) primary and unique constraints. I take it to level S1 because it crashes exiting the app and there is no workaround.
[10 Dec 2011 13:24]
Mike Lischke
Javier, when you start WB next time chose Help -> Locate Log File from the main menu to open an explorer window for the log files. Then repeat your steps until it crahs. Now grab the wb.log file and attach it to this bug report. You can make this attachment private, so only we can see it, if you are concerned about private data. Thank you.
[10 Dec 2011 13:45]
Javier Domingo
This is the error: Nombre del evento de problema: APPCRASH Nombre de la aplicación: MySQLWorkbench.exe Versión de la aplicación: 5.2.36.8542 Marca de tiempo de la aplicación: 4ed8d0ff Nombre del módulo con errores: base.dll Versión del módulo con errores: 0.0.0.0 Marca de tiempo del módulo con errores: 4ed8b9a5 Código de excepción: c0000005 Desplazamiento de excepción: 00013296 Versión del sistema operativo: 6.1.7600.2.0.0.256.48 Id. de configuración regional: 3082 Información adicional 1: 0a9e Información adicional 2: 0a9e372d3b4ad19135b953a78882e789 Información adicional 3: 0a9e Información adicional 4: 0a9e372d3b4ad19135b953a78882e789
[11 Dec 2011 11:27]
Valeriy Kravchuk
Please, send the output of Help > System Info menu item.
[12 Dec 2011 7:12]
Javier Domingo
This is the output: MySQL Workbench CE for Windows version 5.2.36 revision 8542 Configuration Directory: C:\Users\Javier\AppData\Roaming\MySQL\Workbench Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE Cairo Version: 1.8.8 Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering. OpenGL Driver Version: 2.1.0 - Build 8.15.10.2119 OS: Microsoft Windows 7 (build 7600), 64-bit CPU: 4x Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz, 3.8 GiB RAM Active video adapter (0): Intel(R) HD Graphics Installed video RAM: 1719 MB Current video mode: 1366 x 768 x 4294967296 colores Used bit depth: 32 Driver version: 8.15.10.2119 Installed display drivers: igdumd64.dll,igd10umd64.dll,igdumdx32,igd10umd32 Current user language: Español (España, internacional)
[12 Dec 2011 7:59]
Mike Lischke
Javier, the log file you attached is probably already from a new WB session. Everytime you start WB the log files are rotated (wb.log becomes wb.1.log, wb.1.log becomes wb.2.log etc.). So either you see if one of the older log contains the crash info (stack trace and similar) or you start WB again, cause the crash and then take the log file before starting WB again.
[12 Dec 2011 11:04]
Javier Domingo
As I told you, it wont help much. It is the log that appears, checked all of them, and are similar. I deleted all, launched the app, made it crash an that appeared.
[12 Dec 2011 12:58]
Mike Lischke
Oh, so that means the WB process is killed by the OS before it even can log the exception. I guess you don't see our crash window then which asks to report the bug, but just a system provided message, right? Bug #63629 seems to be similar and I fixed that for the next release. Can you check if that is related to your problem?
[12 Dec 2011 14:02]
Javier Domingo
In fact, it is all the time opening the window to report a bug, but as it doesn't crash after, and neither writes anything in the bug submit. If you tell me which env vars do I have to use to get a bigger log, I tell you more. The #63629 could be related, but as I said, it crashes randomly. I have found in a log something interesting. Attaching the file
[12 Dec 2011 16:10]
Mike Lischke
Yes, I see there is an exception logged now. NPE when closing the sql editor. I have added some protection for that today, which will be available with the next release. Please check this then to see if your problem is solved and let us know. For the log: you can adjust the log level, which controls what events are logged. Start WB with the command line option -log-level=debug1 (or any of error, warning, info, debug1, debug2, debug3, from less to more verbose). Alternatively, you can set the environment var "WB_LOG_LEVEL" with any of the mentioned strings to have the same effect. Command line overrides env var, default level is info (which includes error and warning). This also works on Linux + Mac, though the command line option starts with two dashes there, i.e. "--log-level".
[13 Jan 2012 1: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".
