| Bug #63909 | Workbench 5.2.37 crash on startup | ||
|---|---|---|---|
| Submitted: | 3 Jan 2012 9:00 | Modified: | 8 Apr 2012 15:03 |
| Reporter: | olivier piegay | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S1 (Critical) |
| Version: | 5.2.37, 5.2.38 | OS: | Windows (seven 64 bits) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | .net, 5.2.37, crash, startup, wbprivate.be.dll | ||
[3 Jan 2012 9:00]
olivier piegay
[3 Jan 2012 9:36]
Mike Lischke
Olivier, can you start WB with the -log-level=debug3 command line switch and then attach the new log file here? This will hopefully include more info what happens after the init call. Thanks.
[11 Jan 2012 10:31]
[ name withheld ]
Hello, Same problem here, with an up to date Windows XP Professionnal, with both versions 5.2.36 and 5.2.37. Here are the errors I found in the MS Event observer (didn't notice anything into "Application Data\MySQL\Workbench\log\wb.log"): * ".NET Runtime 4.0 error Reporting": Type de l'événement : Erreur Source de l'événement : .NET Runtime 4.0 Error Reporting Catégorie de l'événement : Aucun ID de l'événement : 1000 Date : 11/01/2012 Heure : 11:11:37 Utilisateur : N/A Ordinateur : --- Description : Faulting application mysqlworkbench.exe, version 5.2.37.8576, stamp 4ef3ccea, faulting module msvcr100.dll, version 10.0.30319.415, stamp 4d26c6a1, debug? 0, fault address 0x0007b1a5. Pour plus d'informations, consultez le centre Aide et support à l'adresse http://go.microsoft.com/fwlink/events.asp. Données : 0000: 41 00 70 00 70 00 6c 00 A.p.p.l. 0008: 69 00 63 00 61 00 74 00 i.c.a.t. 0010: 69 00 6f 00 6e 00 20 00 i.o.n. . 0018: 46 00 61 00 69 00 6c 00 F.a.i.l. 0020: 75 00 72 00 65 00 20 00 u.r.e. . 0028: 20 00 6d 00 79 00 73 00 .m.y.s. 0030: 71 00 6c 00 77 00 6f 00 q.l.w.o. 0038: 72 00 6b 00 62 00 65 00 r.k.b.e. 0040: 6e 00 63 00 68 00 2e 00 n.c.h... 0048: 65 00 78 00 65 00 20 00 e.x.e. . 0050: 35 00 2e 00 32 00 2e 00 5...2... 0058: 33 00 37 00 2e 00 38 00 3.7...8. 0060: 35 00 37 00 36 00 20 00 5.7.6. . 0068: 34 00 65 00 66 00 33 00 4.e.f.3. 0070: 63 00 63 00 65 00 61 00 c.c.e.a. 0078: 20 00 69 00 6e 00 20 00 .i.n. . 0080: 6d 00 73 00 76 00 63 00 m.s.v.c. 0088: 72 00 31 00 30 00 30 00 r.1.0.0. 0090: 2e 00 64 00 6c 00 6c 00 ..d.l.l. 0098: 20 00 31 00 30 00 2e 00 .1.0... 00a0: 30 00 2e 00 33 00 30 00 0...3.0. 00a8: 33 00 31 00 39 00 2e 00 3.1.9... 00b0: 34 00 31 00 35 00 20 00 4.1.5. . 00b8: 34 00 64 00 32 00 36 00 4.d.2.6. 00c0: 63 00 36 00 61 00 31 00 c.6.a.1. 00c8: 20 00 66 00 44 00 65 00 .f.D.e. 00d0: 62 00 75 00 67 00 20 00 b.u.g. . 00d8: 30 00 20 00 61 00 74 00 0. .a.t. 00e0: 20 00 6f 00 66 00 66 00 .o.f.f. 00e8: 73 00 65 00 74 00 20 00 s.e.t. . 00f0: 30 00 30 00 30 00 37 00 0.0.0.7. 00f8: 62 00 31 00 61 00 35 00 b.1.a.5. 0100: 0d 00 0a 00 .... ... followed by * ".NET Runtime": Type de l'événement : Erreur Source de l'événement : .NET Runtime Catégorie de l'événement : Aucun ID de l'événement : 1026 Date : 11/01/2012 Heure : 11:11:41 Utilisateur : N/A Ordinateur : --- Description : Application: MySQLWorkbench.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException Stack: at <Module>.base.Logger.log(LogLevel, SByte*, SByte*, ...) at MySQL.Workbench.Logger.LogInfo(System.String, System.String) at MySQL.GUI.Workbench.Program.PrintInitialLogInfo() at MySQL.GUI.Workbench.Program.Main(System.String[]) Pour plus d'informations, consultez le centre Aide et support à l'adresse http://go.microsoft.com/fwlink/events.asp. @Mike Lischke: Where (path ?) do you get the extra debug info given by the "-log-level=debug3" parameter ? I didn't notice any difference in the "Application Data\MySQL\Workbench\log\wb.log" nor into the .NET runtime errors...
[11 Jan 2012 19:29]
Alfredo Kojima
Do you have the 32bit version of the MSVC runtimes installed?
[20 Jan 2012 9:11]
[ name withheld ]
@Alfredo Kojima : I suppose so, as I'm on Windows XP pro 32 bits. But I don't know if the question was for me...
[26 Jan 2012 14:11]
Alfredo Kojima
Please attach the log files at C:\Users\<your user id>\AppData\Roaming\MySQL\Workbench\wb.log
[30 Jan 2012 21:53]
Ammar Khalid
I have the similary problem after an unexpected shut down and now it is not starting up giving same issue as described.
[4 Feb 2012 12:47]
Valeriy Kravchuk
All reporters, Please, locate and upload wb.log file as Alfredo asked in one of the previous comments.
[4 Feb 2012 13:54]
[ name withheld ]
I'll have a wb.log monday, and I must reinstall 5.2.37 before, because I reinstalled a stable version meanwhile (5.2.35). I'll post it as I'll have it, but when I posted my logs in a previous comment, this wb.log didn't have anything talking about an error... PS: the bug description should change and "Windows XP pro (32 bits)" should be added to the OS list... PPS: I don't know if it would help, but the crash occured on a Dell desktop PC, it means it was on a "Dell" Windows XP pro ! I'm not sure that makes a difference...
[20 Feb 2012 15:59]
Jorge Pinho
Hi, I have posted on an old report 41930, but I believe this is the place. I started having this problem after a power failure. It crashes when I connect (double-click) on the "local instance", I can start a new model and open the server admin with no problems. If I choose "command line" everything is fine, and I can work perfectly. If I create another connection to the same server (and credencials), everyting is fine! I have Win7-64, MySQL 5.5, and WB 5.2.34 CE 7780 full wp.log: 15:17:09 [ Info][ wbprivate]: WbContext::init 15:17:10 [ Info][ (null)]: Found auto-save workspace C:\Users\jorgepinho\AppData\Roaming\MySQL\Workbench\sql_workspaces\Local_instance_MySQL55-1.autosave 15:53:12 [ Info][ wbprivate]: Starting tunnel Info from SO (in portuguese): Assinatura do problema: Nome do Evento de Problema: APPCRASH Nome da aplicação: MySQLWorkbench.exe Versão da aplicação: 5.2.34.7780 Carimbo de Data/Hora da Aplicação: 4ddbbfe9 Nome do Módulo com Falhas: wbprivate.be.dll Versão do Módulo com Falhas: 0.0.0.0 Carimbo de Data/Hora do Módulo com Falhas: 4ddbbeb7 Código de excepção: c0000005 Desvio de Excepção: 000070ce Versão do SO: 6.1.7601.2.1.0.256.48 ID de Região: 2070 Informações Adicionais 1: 0a9e Informações Adicionais 2: 0a9e372d3b4ad19135b953a78882e789 Informações Adicionais 3: 0a9e Informações Adicionais 4: 0a9e372d3b4ad19135b953a78882e789
[24 Feb 2012 12:10]
Valeriy Kravchuk
Please, check if the same problem still happens with a newer version, 5.2.38.
[24 Feb 2012 14:07]
[ name withheld ]
I tried 5.2.37 and 5.2.38, they don't even write anything in wb.log before crashing (file not even touched) !
[8 Mar 2012 13:03]
Alfredo Kojima
Can you try running some other OpenGL application and see if it works?
[8 Mar 2012 13:34]
[ name withheld ]
I tried Google Earth in OpenGL and it works perfectly.
[8 Mar 2012 13:51]
Alfredo Kojima
scrouzil, your problem is different. Did you install VC++2010 runtimes for 32bits and .NET 4?
[8 Mar 2012 14:31]
[ name withheld ]
@Alfredo Kojima : Sorry for that. I have installed both, and re-installed MySQL wb 5.2.38, same error.
[8 Mar 2012 15:03]
Alfredo Kojima
scouzil, pls open a new bug for you issue (including a note saying the log file is empty).
[9 Apr 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".
