Wxwidgets debug alert - Githubissues

LaytonXV commented 4 years ago

After a few minutes (sometimes after a few seconds) I started WxMaxima, the application crashes with the follwing error: "wxwidgets debug alert" without showing me anything else. These continuous crashes do not allow me to work and I am forced to save every few seconds (often without success). I tried to reinstall several times (also older versions) but nothing to do.

This is the information that maxima asks me to include with my bug report:

_wxMaxima version: 20.06.6_MSW_OpenMP201511+Locks using wxWidgets version: wxWidgets 3.1.3 Maxima version: 5.44.0 Maxima build date: 2020-06-08 22:46:53 Host type: x8664-w64-mingw32 System type: Win32 6.2.9200 X86-64 Lisp implementation type: SBCL Lisp implementation version: 2.0.0 wxMaxima's idea of the directory layout is: User configuration dir: C:\Users\Nome Cognome/maxima/ Help dir: C:\maxima-5.44.0\share/doc/wxmaxima

Please help me find a solution and thanks in advance !!

LaytonXV commented 4 years ago

After a few minutes (sometimes after a few seconds) I started WxMaxima, the application crashes with the follwing error: "wxwidgets debug alert" without showing me anything else. These continuous crashes do not allow me to work and I am forced to save every few seconds (often without success). I tried to reinstall several times (also older versions) but nothing to do.

This is the information that maxima asks me to include with my bug report:

_wxMaxima version: 20.06.6_MSW_OpenMP201511+Locks using wxWidgets version: wxWidgets 3.1.3 Maxima version: 5.44.0 Maxima build date: 2020-06-08 22:46:53 Host type: x8664-w64-mingw32 System type: Win32 6.2.9200 X86-64 Lisp implementation type: SBCL Lisp implementation version: 2.0.0 wxMaxima's idea of the directory layout is: User configuration dir: C:\Users\Nome Cognome/maxima/ Help dir: C:\maxima-5.44.0\share/doc/wxmaxima

Please help me find a solution and thanks in advance !!

gunterkoenigsmann commented 4 years ago

@KubaO has done much work on making wxMaxima more reliable => I hope that the wxMaxima version you can find at https://wolfgang.dautermann.at/maxima/nightlybuild/ resolves that problem.

KubaO commented 4 years ago

This is something specific to your system, sorry. It may be impossible to debug without remote access to your system. Could you please provide exact version of Windows and hardware configuration? A complete output of sysinfo would be perfect.

30 sep. 2020 kl. 12:08 em skrev LaytonXV notifications@github.com:

After a few minutes (sometimes after a few seconds) I started WxMaxima, the application crashes with the follwing error: "wxwidgets debug alert" without showing me anything else. These continuous crashes do not allow me to work and I am forced to save every few seconds (often without success). I tried to reinstall several times (also older versions) but nothing to do.

This is the information that maxima asks me to include with my bug report:

wxMaxima version: 20.06.6_MSW_OpenMP201511+Locks using wxWidgets version: wxWidgets 3.1.3 Maxima version: 5.44.0 Maxima build date: 2020-06-08 22:46:53 Host type: x86_64-w64-mingw32 System type: Win32 6.2.9200 X86-64 Lisp implementation type: SBCL Lisp implementation version: 2.0.0 wxMaxima's idea of the directory layout is: User configuration dir: C:\Users\Nome Cognome/maxima/ Help dir: C:\maxima-5.44.0\share/doc/wxmaxima

Please help me find a solution and thanks in advance !!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

LaytonXV commented 4 years ago

@gunterkoenigsmann I have already tried to install this version but I get the same error.

@KubaO has done much work on making wxMaxima more reliable => I hope that the wxMaxima version you can find at https://wolfgang.dautermann.at/maxima/nightlybuild/ resolves that problem.

LaytonXV commented 4 years ago

@KubaO Here the sysinfo

Screenshot (5)

This is something specific to your system, sorry. It may be impossible to debug without remote access to your system. Could you please provide exact version of Windows and hardware configuration? A complete output of sysinfo would be perfect. … 30 sep. 2020 kl. 12:08 em skrev LaytonXV @.***>: After a few minutes (sometimes after a few seconds) I started WxMaxima, the application crashes with the follwing error: "wxwidgets debug alert" without showing me anything else. These continuous crashes do not allow me to work and I am forced to save every few seconds (often without success). I tried to reinstall several times (also older versions) but nothing to do. This is the information that maxima asks me to include with my bug report: wxMaxima version: 20.06.6_MSW_OpenMP201511+Locks using wxWidgets version: wxWidgets 3.1.3 Maxima version: 5.44.0 Maxima build date: 2020-06-08 22:46:53 Host type: x86_64-w64-mingw32 System type: Win32 6.2.9200 X86-64 Lisp implementation type: SBCL Lisp implementation version: 2.0.0 wxMaxima's idea of the directory layout is: User configuration dir: C:\Users\Nome Cognome/maxima/ Help dir: C:\maxima-5.44.0\share/doc/wxmaxima Please help me find a solution and thanks in advance !! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

KubaO commented 4 years ago

Hmm. I’m running it without issues on a very similar system configuration. Since many different wxMaxima versions are affected as you say, I suggest two things:

Temporarily remove any third party antivirus products if you have them installed.
Clear wxMaxima settings: run registry editor, go to current user -> software, and delete the entire wxMaxima key there (be careful not to remove anything else).

If that won’t help, then we’ll need to try some alternative approaches. The first one would be to use a wxMaxima built using another compiler - this may be some sort of a MinGW bug in action.

Cheers, Kuba

1 okt. 2020 kl. 3:23 fm skrev LaytonXV notifications@github.com:

@KubaO Here the sysinfo

This is something specific to your system, sorry. It may be impossible to debug without remote access to your system. Could you please provide exact version of Windows and hardware configuration? A complete output of sysinfo would be perfect. … 30 sep. 2020 kl. 12:08 em skrev LaytonXV @.***>: After a few minutes (sometimes after a few seconds) I started WxMaxima, the application crashes with the follwing error: "wxwidgets debug alert" without showing me anything else. These continuous crashes do not allow me to work and I am forced to save every few seconds (often without success). I tried to reinstall several times (also older versions) but nothing to do. This is the information that maxima asks me to include with my bug report: wxMaxima version: 20.06.6_MSW_OpenMP201511+Locks using wxWidgets version: wxWidgets 3.1.3 Maxima version: 5.44.0 Maxima build date: 2020-06-08 22:46:53 Host type: x86_64-w64-mingw32 System type: Win32 6.2.9200 X86-64 Lisp implementation type: SBCL Lisp implementation version: 2.0.0 wxMaxima's idea of the directory layout is: User configuration dir: C:\Users\Nome Cognome/maxima/ Help dir: C:\maxima-5.44.0\share/doc/wxmaxima Please help me find a solution and thanks in advance !! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

gunterkoenigsmann commented 4 years ago

On MS Windows there is a 2nd factor that can lead to recurring, persisting problems: If two versions of wxMaxima are installed on the same system sometimes windows starts the old wxMaxima when the user expects the new one to start. In other instants the problem could be resolved by collecting enough puzzle pieces about the condition that triggers the bug until the bug could be narrowed down to a small piece of code - that actually contained the bug.

KubaO commented 4 years ago

So far all we have confirmation for is version 20.06.6, for sure.

1 okt. 2020 kl. 1:01 em skrev Gunter Königsman notifications@github.com:

On MS Windows there is a 2nd factor that can lead to recurring, persisting problems: If two versions of wxMaxima are installed on the same system sometimes windows starts the old wxMaxima when the user expects the new one to start. In other instants the problem could be resolved by collecting enough puzzle pieces about the condition that triggers the bug until the bug could be narrowed down to a small piece of code - that actually contained the bug.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

LaytonXV commented 4 years ago

First of all thank you all for the help.

@KubaO i followed your instructions with the antivirus and cleaning wxmaxima settings but nothing to do;

@gunterkoenigsmann I currently only installed one version of wxmaxima, moreover I had encountered this bug after the first installation without writing anything in wxmaxima;

I would like to tell you something that I noticed and I can't explain why: throughout the morning the program always crashes after a few seconds or at most minutes. During the afternoon, on the other hand, ( sometimes without changing anything ), the program works for several hours (also 4/5 hours) without crashing. This makes me seem to be able to solve the problem but during the night and again in the morning it starts to crash again after a few seconds. I know of course that the times have nothing to do with it but it seemed strange to me so I thought I'd say it.

KubaO commented 4 years ago

Please install the newest version and try again. Yours is from June.

1 okt. 2020 kl. 3:16 em skrev LaytonXV notifications@github.com:

First of all thank you all for the help.

@KubaO i followed your instructions with the antivirus and cleaning wxmaxima settings but nothing to do;

@gunterkoenigsmann I currently only installed one version of wxmaxima, moreover I had encountered this bug after the first installation without writing anything in wxmaxima;

I would like to tell you something that I noticed and I can't explain why: throughout the morning the program always crashes after a few seconds or at most minutes. During the afternoon, on the other hand, ( sometimes without changing anything ), the program works for several hours (also 4/5 hours) without crashing. This makes me seem to be able to solve the problem but during the night and again in the morning it starts to crash again after a few seconds. I know of course that the times have nothing to do with it but it seemed strange to me so I thought I'd say it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

LaytonXV commented 4 years ago

@KubaO the newest version that i can see is the 5.44.0 from June.

LaytonXV commented 4 years ago

@KubaO the newest version that i can see is the 5.44.0 from June.

The other version (2020-10-01) is the untested one that I tried to install a few days ago on the site : https://wolfgang.dautermann.at/maxima/nightlybuild/

gunterkoenigsmann commented 4 years ago

Most of the times errors persisting when using that version are caused by windows still using the old version of wxMaxima even if a new one is installed on the same system.

LaytonXV commented 4 years ago

Most of the times errors persisting when using that version are caused by windows still using the old version of wxMaxima even if a new one is installed on the same system.

What should I do to understand if this is the case and then fix it ?

gunterkoenigsmann commented 4 years ago

The easiest way is: First uninstall the old wxMaxima and then install the new one from dautermann.at.

Kind regards,

Gunter.

LaytonXV commented 4 years ago

Okay but that's what I've been trying to do for days... I'll try again.

The easiest way is: First uninstall the old wxMaxima and then install the new one from dautermann.at.

Kind regards,

Gunter.

gunterkoenigsmann commented 4 years ago

What does the dautermann version output if you type

   build_info()

?

gunterkoenigsmann commented 4 years ago

If that doesn't give us a hint: Can you enable the debug messages sidebar and look what seems to be the last debug message before the crash? Or can you get a glimpse of the text in the debug message window that tries to tell what is wrong?

If all that fails: You don't happen to have a 64bit gdb installed like the one that comes with mingw64?

gdb allows to make backtracked of crashes. In other words: It tells you in which line of code the program crashed and how it got there. Having this info and/or a hint on what triggers the crash often allows to resolve crashes within less than 5 minutes. Without any hint on what went wrong all that can be done is to look at all of the code and search for bugs. Which is what Kuba did for the last few months and in all the things I use of wxMaxima with great success: in the last few working days I found exactly zero bugs.

Another idea: I believe I added a feature to the config dialogue that Allows to export (hopefully)all settings to a file. Could you send us such a file? Perhaps you are using a combination of settings we happened never to use long enough to trigger the bug...

LaytonXV commented 4 years ago

What does the dautermann version output if you type
   build_info()
?

After deleting and uninstalling the program and any references to maxima and wxmaxima and after uninstalling the third party antivirus I restarted the pc and downloaded again the latest version of wxmaxima from the site https://wolfgang.dautermann.at/maxima/nightlybuild/. The informations are:

_wxMaxima version: 20.09.0-DevelopmentSnapshot_MSW_OpenMP201511+Locks using wxWidgets version: wxWidgets 3.1.4 Maxima version: branch_5_44_base_79_g835adc1aa Maxima build date: 2020-10-02 00:05:39 Host type: x8664-w64-mingw32 System type: Win32 6.2.9200 X86-64 Lisp implementation type: SBCL Lisp implementation version: 2.0.0 wxMaxima's idea of the directory layout is: User configuration dir: C:\Users\Ethan Bernardini/maxima/ Help dir: C:\maxima-current\share/doc/wxmaxima

The build info is:

_version="branch_5_44_base_79_g835adc1aa",timestamp="2020-10-02 00:05:39",host="x86_64-w64-mingw32",lisp_name="SBCL",lisp_version="2.0.0",maxima_userdir="C:/Users/Nome Cognome/maxima",maxima_tempdir="C:/Users/Nome Cognome/AppData/Local/Temp",maxima_objdir="C:/Users/Nome Cognome/maxima/binary/branch_5_44_base_79_g835adc1aa/sbcl/2_0_0",maxima_frontend="wxMaxima",maxima_frontend_version="20.09.0-DevelopmentSnapshot_MSWOpenMP201511+Locks")" "

LaytonXV commented 4 years ago

The last few times I tried to notice if some messages appeared in the debug ones before the bug but the last one always remained the same. Here the list of debug messages (I don't know why the last part is shown with a line):

17:07:13: wxMaxima version 20.09.0-DevelopmentSnapshot 17:07:13: Running on MS Windows using DirectDraw 17:07:13: OS: Windows 10 (build 19041), 64-bit edition Version 10.0 17:07:13: wxWidgets 3.1.4 17:07:13: Translations are read from C:\maxima-current\share/locale. 17:07:13: Reading the config from the default location. 17:07:13: FontCache Raw Miss: 10,00pt ---- "Linux Libertine G" fam:70 enc:0 17:07:13: FontCache Resolved: 10,00pt ---- "Linux Libertine G" fam:74 enc:-1 17:07:13: Error: XML parsing error: 'no element found' at line 1 17:07:13: Error: XML parsing error: 'no element found' at line 1 17:07:13: Gnuplot found at: C:\maxima-current\bin..\gnuplot\bin\gnuplot.exe 17:07:13: Selected language: it_IT (109) 17:07:13: Starting server on port 49152 17:07:13: Server started 17:07:13: Running maxima as: "C:\maxima-current\bin\maxima.bat" -s 49152 17:07:13: Maxima started. Waiting for connection... 17:07:13: Welcome to wxMaxima 17:07:13: Setting a few prerequisites for wxMaxima 17:07:13: Sending maxima the info how to express 2d maths as XML 17:07:13: Updating maxima's configuration 17:07:13: Sending configuration data to maxima. 17:07:13: Received maxima's first prompt: pid=4708â†²Maxima branch_5_44_base_79_g835adc1aa http://maxima.sourceforge.netâ†²using Lisp SBCL 2.0.0â†²Distributed under the GNU Public License. See the file COPYING.â†²Dedicated to the memory of William Schelter.â†²The function bug_report() provides bug reporting information.â†²(11) 17:07:13: Maxima's PID is 4708 17:07:13: Ready for user input 17:07:13: Maxima is ready for input. 17:07:14: Scheduling a background task that compiles a new list of autocompletible maxima commands. 17:07:14: Maxima user configuration lies in directory C:/Users/Nome Cognome/maxima 17:07:14: Maxima uses temp directory C:/Users/Nome Cognome/AppData/Local/Temp 17:07:14: Maxima's manual lies in directory C:/maxima-current/share/info 17:07:14: Gnuplot found at: C:\maxima-current\bin..\gnuplot\bin\gnuplot.exe 17:07:14: Querying gnuplot which graphics drivers it supports. 17:07:14: Maxima version: branch_5_44_base_79_g835adc1aa 17:07:14: Maxima's share files lie in directory C:/maxima-current/share/maxima/branch_5_44_base_79_g835adc1aa/share 17:07:14: Scheduling a background task that setups the autocomplete builtins list. 17:07:14: Scheduling a background task that setups the autocompletable files list. 17:07:14: Read the entries the maxima manual offers from C:/Users/Nome Cognome/maxima//manual_anchors.xml 17:07:14: Maxima architecture: x86_64-w64-mingw32 17:07:14: Maxima was compiled using SBCL 17:07:14: Lisp version: 2.0.0 17:07:14: Maxima sends a new set of auto-completable symbols. 17:07:14: Maxima sends a new set of auto-completable symbols. 17:07:14: Autocompletion: Scanning C:\maxima-current\share\maxima\branch_5_44_base_79_g835adc1aa\share\ recursively for loadable lisp files. 17:07:14: Trying to load a list of autocompletible symbols from file C:/Users/Nome Cognome/maxima/wxmaxima.ac 17:07:14: Autocompletion: Scanning C:\Users\Nome Cognome\maxima\ for loadable lisp files. 17:07:14: Found 1037 loadable files. 17:07:14: Autocompletion: Scanning C:\maxima-current\share\maxima\branch_5_44_base_79_g835adc1aa\ for loadable demo files. 17:07:14: Found 111 demo files. 17:07:14: Terminals supported by gnuplot: caca cairolatex canvas cgm context domterm dumb dxf eepic emf emtex epscairo epslatex fig gif hpgl jpeg latex lua mf mp pcl5 pdfcairo png pngcairo postscript pslatex pstex pstricks qms qt sixelgd svg texdraw tgif tikz tkcanvas tpic unknown windows wxt 17:07:14: Using gnuplot's pngcairo driver for embedded plots 17:13:01: FontCache Raw Miss: 10,80pt BI-- "Arial" fam:70 enc:0 17:13:01: FontCache Resolved: 10,80pt BI-- "Arial" fam:74 enc:-1 17:13:01: FontCache Raw Miss: 10,80pt ---- "Arial" fam:70 enc:0 17:13:01: FontCache Resolved: 10,80pt ---- "Arial" fam:74 enc:-1 17:13:01: FontCache Raw Miss: 12,00pt ---- "Arial" fam:70 enc:0 17:13:01: FontCache Resolved: 12,00pt ---- "Arial" fam:74 enc:-1 17:13:01: FontCache Raw Miss: 10,80pt -I-- "Linux Libertine O" fam:70 enc:0 17:13:01: FontCache Resolved: 10,80pt -I-- "Linux Libertine O" fam:74 enc:-1 17:13:01: FontCache Raw Miss: 10,80pt ---- "Linux Libertine O" fam:70 enc:0 17:13:01: FontCache Resolved: 10,80pt ---- "Linux Libertine O" fam:74 enc:-1 17:13:01: FontCache Raw Miss: 20,00pt ---- "Linux Libertine O" fam:70 enc:0 17:13:01: FontCache Resolved: 20,00pt ---- "Linux Libertine O" fam:74 enc:-1 17:13:01: FontCache Raw Miss: 20,00pt ---- "Linux Libertine" fam:70 enc:0 17:13:01: FontCache Resolved: 20,00pt ---- "Linux Libertine" fam:74 enc:-1 17:13:01: Maxima is ready for input. 17:13:01: Maxima sends a new set of auto-completable symbols. 17:13:06: FontCache Raw Miss: 10,80pt ---- "Linux Libertine" fam:70 enc:0 17:13:06: FontCache Resolved: 10,80pt ---- "Linux Libertine" fam:74 enc:-1 17:13:06: Maxima sends a new set of auto-completable symbols. 17:13:06: Maxima is ready for input. 17:13:21: Starting to save the worksheet as .wxmx 17:13:21: wxmx file saved 17:13:21: Autosaving as temp file C:\Users\NOMEC~1\AppData\Local\Temp/untitled_2060_4708.wxmx 17:15:06: Killing Maxima. 17:15:06: Error: Failed to kill process 4708 (error 5: Accesso negato.) 17:15:06: Error: Failed to kill process 4708 (error 5: Accesso negato.) 17:15:06: Sending a wxSIGKILL to maxima has failed 17:15:06: Running maxima as: "C:\maxima-current\bin\maxima.bat" -s 49152 17:15:06: Maxima started. Waiting for connection... 17:15:06: Setting a few prerequisites for wxMaxima 17:15:06: Sending maxima the info how to express 2d maths as XML 17:15:06: Updating maxima's configuration 17:15:06: Sending configuration data to maxima. 17:15:06: Received maxima's first prompt: pid=15224â†²Maxima branch_5_44_base_79_g835adc1aa http://maxima.sourceforge.netâ†²using Lisp SBCL 2.0.0â†²Distributed under the GNU Public License. See the file COPYING.â†²Dedicated to the memory of William Schelter.â†²The function bug_report() provides bug reporting information.â†²(11) 17:15:06: Maxima's PID is 15224 17:15:07: Scheduling a background task that compiles a new list of autocompletible maxima commands. 17:15:07: Maxima user configuration lies in directory C:/Users/Nome Cognome/maxima 17:15:07: Maxima uses temp directory C:/Users/Nome Cognome/AppData/Local/Temp 17:15:07: Maxima's manual lies in directory C:/maxima-current/share/info 17:15:07: Gnuplot found at: C:\maxima-current\bin..\gnuplot\bin\gnuplot.exe 17:15:07: Querying gnuplot which graphics drivers it supports. 17:15:07: Maxima version: branch_5_44_base_79_g835adc1aa 17:15:07: Maxima's share files lie in directory C:/maxima-current/share/maxima/branch_5_44_base_79_g835adc1aa/share 17:15:07: Scheduling a background task that setups the autocomplete builtins list. 17:15:07: Scheduling a background task that setups the autocompletable files list. 17:15:07: Maxima architecture: x86_64-w64-mingw32 17:15:07: Maxima was compiled using SBCL 17:15:07: Lisp version: 2.0.0 17:15:07: Maxima sends a new set of auto-completable symbols. 17:15:07: Maxima sends a new set of auto-completable symbols. 17:15:07: Autocompletion: Scanning C:\maxima-current\share\maxima\branch_5_44_base_79_g835adc1aa\share\ recursively for loadable lisp files. 17:15:07: Trying to load a list of autocompletible symbols from file C:/Users/Nome Cognome/maxima/wxmaxima.ac 17:15:07: Ready for user input 17:15:07: Maxima is ready for input. 17:15:07: Maxima sends a new set of auto-completable symbols. 17:15:07: Autocompletion: Scanning C:\Users\Nome Cognome\maxima\ for loadable lisp files. 17:15:07: Found 1037 loadable files. 17:15:07: Autocompletion: Scanning C:\maxima-current\share\maxima\branch_5_44_base_79_g835adc1aa\ for loadable demo files. 17:15:07: Found 111 demo files. 17:15:07: Terminals supported by gnuplot: caca cairolatex canvas cgm context domterm dumb dxf eepic emf emtex epscairo epslatex fig gif hpgl jpeg latex lua mf mp pcl5 pdfcairo png pngcairo postscript pslatex pstex pstricks qms qt sixelgd svg texdraw tgif tikz tkcanvas tpic unknown windows wxt 17:15:07: Using gnuplot's pngcairo driver for embedded plots 17:16:21: Starting to save the worksheet as .wxmx 17:16:21: wxmx file saved 17:16:21: Autosaving as temp file C:\Users\NOMEC~1\AppData\Local\Temp/untitled_2060_15224.wxmx 17:16:21: Trying to remove the old temp file C:\Users\NOMEC~1\AppData\Local\Temp/untitled_2060_4708.wxmx

gunterkoenigsmann commented 4 years ago

In the meantime I've done the following things hoping to find the problem and to fix it:

I've found out how to make the new code analysis tool github offers work for us. That tool actually found three hard-to-trigger bugs ("hard-to-trigger bug" sounds good, as only a few users are affected. But it also means that it is hard to find and to fix the bug). But I believe none of the bugs is the one you trigger.
I've added a "Export the config" button to the "configuration" dialogue => If the configuration is somehow involved in triggering the problem you can now send us your configuration in order to allow us to crash wxMaxima, too.
Additionally I made the "Reset all to defaults" button work for all settings. At least I hope so.
And I found a way to crash wxMaxima on copy-and-paste and resolved that. With a bit of luck this actually resolves your problem.

gunterkoenigsmann commented 4 years ago

Hmmm... ...one of the debug messages suggests that something is severely wrong with the .wxmx file you are working with. Perhaps that might be a hint. Would you be willing to send me that file to gunter (at) peterpall.de so I can see if we can find the error somehow in its internal structure?

wxMaxima-developers / wxmaxima

Wxwidgets debug alert #1404