search

kpeeters / cadabra2

A field-theory motivated approach to computer algebra.
https://cadabra.science/
GNU General Public License v3.0
228 stars 37 forks source link

Windows build of cadabra2.2.1 crashed after the start on win10 #114

Closed mzavadil closed 4 years ago

mzavadil commented 5 years ago

After the start application is shown its window for 2-3 seconds (does not respond on mouse) and then closed by inner crash. In EventLogs is:

Faulting application name: cadabra2-gtk.exe, version: 0.0.0.0, time stamp: 0x5b7ae39e
Faulting module name: ucrtbase.dll, version: 10.0.17763.1, time stamp: 0x309241e0
Exception code: 0xc0000409
Fault offset: 0x000000000006f08e
Faulting process id: 0x6614
Faulting application start time: 0x01d46010c7347c9c
Faulting application path: C:\Program Files\Cadabra2\bin\cadabra2-gtk.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 623a9384-578d-487b-b216-aa4d8af9c1b9
Faulting package full name: 
Faulting package-relative application ID:

and

Fault bucket 1588973600808251271, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: cadabra2-gtk.exe
P2: 0.0.0.0
P3: 5b7ae39e
P4: ucrtbase.dll
P5: 10.0.17763.1
P6: 309241e0
P7: 000000000006f08e
P8: c0000409
P9: 0000000000000007
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41DF.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER425D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER426D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER426D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER428E.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_cadabra2-gtk.exe_8fc92a11d272822f738eac3b4b95316063af36f6_48d29fd4_67804692

Analysis symbol: 
Rechecking for solution: 0
Report Id: 623a9384-578d-487b-b216-aa4d8af9c1b9
Report Status: 268435456
Hashed bucket: c507e74d4eaaffd3460d2b1239a62f87
Cab Guid: 0

Report.wer.txt

cadabra2-gtk.exe.28900.zip

kpeeters commented 5 years ago

Did you build it from source yourself or is this from a binary installer?

mzavadil commented 5 years ago

I installed binnary package from: https://cadabra.science/packages/windows/

BTW:

kpeeters commented 5 years ago

Do you have a 64 bit Anaconda Python installed?

mzavadil commented 5 years ago

Do you have a 64 bit Anaconda Python installed?

Yes, this version: _Anaconda3-5.3.0-Windows-x8664.exe and MikTeX 2.9.6840 64-bit

mzavadil commented 5 years ago

FYI: the clean build from source code is fully functional on the same computer.

kpeeters commented 5 years ago

Ok, that's good to know. The problem you saw may have something to do with cadabra-server not starting properly. You may want to try that from a command line; it should spit out a single number and then wait. If it fails to do that, that's the cause.

mzavadil commented 5 years ago

I fixed the problem with Cadabra2 initialization by setting the environment variable PYTHONHOME to Anaconda3 installation path. See:

https://stackoverflow.com/questions/5694706/py-initialize-fails-unable-to-load-the-file-system-codec or https://stackoverflow.com/questions/38380310/py-initialize-crash-on-windows-os

I guess: maybe it helped make the call Py_SetPythonHome in the source code before Py_InitializeEx

kpeeters commented 5 years ago

This will need some care as I am sure it easy to mess this up (the key thing being that we need to figure out what PYTHONHOME should be, reliably, on all platforms). When I have time again...

kpeeters commented 4 years ago

This should be fixed with the current Windows installer (2.2.7g); please re-open this issue if there are still problems.