Save a File crashes #635
Labels
Milestone
Comments
|
@standera that's certainly strange. To help us debug, can you add some more info, please?
Thanks |
|
PS feel free to add screenshots if you think it will help |
|
Also, please click on the cog icon in the bottom right of the editor and paste the content of the log file. Log files are recreated each day, so make sure you have recently crashed Mu. This is really odd... since we've never had any problems in any Windows version for saving a file to the filesystem. This suggests the problem may be local to your setup. Are you using a machine that is perhaps "locked down" by school/work? Is there anything about your Windows setup that makes it different to a default install? Perhaps you're using a certain sort of anti-virus software (I'm clutching at straws here, but I'm trying to think of applications which may interfere with the workings of Mu). The more information you can provide, the easier it'll be for us to identify the cause. The log file is key to this. Thank you! Having bug reports like yours is so helpful to making Mu a better editor. |
|
Hi,
thanks for your answer.
Do you have a micro:bit plugged in at the time?
Actually it does not matter. The crash is across all modes (Python, MicroBit,...)
When you say "the crash window" -- do you mean the generic Microsoft [This application has stopped responding] popup? Or something else?
Yes I think so. See the picture bellow (only the Czech version).
Can you confirm where you're downloading the editor from, please?
Official site of the Mu Editor, downloaded 2 days ago.
If you have access to any other Windows machine, have you tried there and seen the same or different results?
Sorry, no other windows machine (My Mac version works perfectly well).
Question: In some cases windows do not like non ASCII characters in account name (In my case the character "Š"). Could not it be the problem?
Sorry for my English :-)
Štanderovi, Nový Bor
Dne 04. 9.. 2018 v 11:59 uživatel Tim Golden <[email protected]> napsal(a):
@standera that's certainly strange. To help us debug, can you add some more info, please?
Do you have a micro:bit plugged in at the time?
When you say "the crash window" -- do you mean the generic Microsoft [This application has stopped responding] popup? Or something else?
Can you confirm where you're downloading the editor from, please?
If you have access to any other Windows machine, have you tried there and seen the same or different results?
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@standera if you copy and paste the log file after Mu crashes (see my previous instructions above), we'll be able to confirm your hunch about non ASCII characters in the account name. ;-) |
|
2018-09-05 08:09:27,583 - root:112(run) INFO:
…-----------------
Starting Mu 1.0.0
2018-09-05 08:09:27,599 - root:113(run) INFO: uname_result(system='Windows', node='MyDELL', release='8.1', version='6.3.9600', machine='AMD64', processor='Intel64 Family 6 Model 60 Stepping 3, GenuineIntel')
2018-09-05 08:09:27,599 - root:114(run) INFO: Python path: ['C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\Python\\python36.zip', 'C:\\Program Files\\Mu\\Python', 'C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\pkgs\\IPython\\extensions']
2018-09-05 08:09:28,364 - mu.logic:540(__init__) INFO: Setting up editor.
2018-09-05 08:09:28,364 - mu.logic:558(__init__) INFO: Settings path: C:\Users\MIROSL~1\AppData\Local\python\mu\settings.json
2018-09-05 08:09:28,364 - mu.logic:559(__init__) INFO: Session path: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:09:28,364 - mu.logic:560(__init__) INFO: Log directory: C:\Users\MIROSL~1\AppData\Local\python\mu\Logs
2018-09-05 08:09:28,364 - mu.logic:561(__init__) INFO: Data directory: C:\Users\MIROSL~1\AppData\Local\python\mu
2018-09-05 08:09:28,379 - mu.logic:574(setup) INFO: Available modes: python, adafruit, microbit, debugger, pygamezero
2018-09-05 08:09:30,037 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:09:30,037 - mu.logic:623(restore_session) INFO: Restoring session from: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:09:30,037 - mu.logic:624(restore_session) DEBUG: {'theme': 'day', 'mode': 'microbit', 'paths': [], 'envars': [], 'minify': False, 'microbit_runtime': ''}
2018-09-05 08:09:30,037 - mu.logic:645(restore_session) INFO: Loaded files.
2018-09-05 08:09:30,037 - mu.logic:649(restore_session) INFO: User defined environment variables: []
2018-09-05 08:09:30,037 - mu.logic:653(restore_session) INFO: Minify scripts on micro:bit? False
2018-09-05 08:09:30,566 - mu.logic:671(restore_session) INFO: Starting with blank file.
2018-09-05 08:09:30,613 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:09:33,895 - mu.logic:1067(select_mode) INFO: Showing available modes: ['python', 'adafruit', 'microbit', 'debugger', 'pygamezero']
2018-09-05 08:09:38,220 - mu.logic:1072(select_mode) INFO: New mode selected: python
2018-09-05 08:09:38,251 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:12:09,634 - root:112(run) INFO:
-----------------
Starting Mu 1.0.0
2018-09-05 08:12:09,634 - root:113(run) INFO: uname_result(system='Windows', node='MyDELL', release='8.1', version='6.3.9600', machine='AMD64', processor='Intel64 Family 6 Model 60 Stepping 3, GenuineIntel')
2018-09-05 08:12:09,634 - root:114(run) INFO: Python path: ['C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\Python\\python36.zip', 'C:\\Program Files\\Mu\\Python', 'C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\pkgs\\IPython\\extensions']
2018-09-05 08:12:09,759 - mu.logic:540(__init__) INFO: Setting up editor.
2018-09-05 08:12:09,759 - mu.logic:558(__init__) INFO: Settings path: C:\Users\MIROSL~1\AppData\Local\python\mu\settings.json
2018-09-05 08:12:09,759 - mu.logic:559(__init__) INFO: Session path: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:12:09,759 - mu.logic:560(__init__) INFO: Log directory: C:\Users\MIROSL~1\AppData\Local\python\mu\Logs
2018-09-05 08:12:09,759 - mu.logic:561(__init__) INFO: Data directory: C:\Users\MIROSL~1\AppData\Local\python\mu
2018-09-05 08:12:09,775 - mu.logic:574(setup) INFO: Available modes: python, adafruit, microbit, debugger, pygamezero
2018-09-05 08:12:10,165 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:12:10,165 - mu.logic:623(restore_session) INFO: Restoring session from: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:12:10,165 - mu.logic:624(restore_session) DEBUG: {'theme': 'day', 'mode': 'microbit', 'paths': [], 'envars': [], 'minify': False, 'microbit_runtime': ''}
2018-09-05 08:12:10,165 - mu.logic:645(restore_session) INFO: Loaded files.
2018-09-05 08:12:10,165 - mu.logic:649(restore_session) INFO: User defined environment variables: []
2018-09-05 08:12:10,165 - mu.logic:653(restore_session) INFO: Minify scripts on micro:bit? False
2018-09-05 08:12:10,540 - mu.logic:671(restore_session) INFO: Starting with blank file.
2018-09-05 08:12:10,556 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:15:23,174 - root:112(run) INFO:
-----------------
Starting Mu 1.0.0
2018-09-05 08:15:23,174 - root:113(run) INFO: uname_result(system='Windows', node='MyDELL', release='8.1', version='6.3.9600', machine='AMD64', processor='Intel64 Family 6 Model 60 Stepping 3, GenuineIntel')
2018-09-05 08:15:23,174 - root:114(run) INFO: Python path: ['C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\Python\\python36.zip', 'C:\\Program Files\\Mu\\Python', 'C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\pkgs\\IPython\\extensions']
2018-09-05 08:15:23,280 - mu.logic:540(__init__) INFO: Setting up editor.
2018-09-05 08:15:23,280 - mu.logic:558(__init__) INFO: Settings path: C:\Users\MIROSL~1\AppData\Local\python\mu\settings.json
2018-09-05 08:15:23,280 - mu.logic:559(__init__) INFO: Session path: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:15:23,280 - mu.logic:560(__init__) INFO: Log directory: C:\Users\MIROSL~1\AppData\Local\python\mu\Logs
2018-09-05 08:15:23,280 - mu.logic:561(__init__) INFO: Data directory: C:\Users\MIROSL~1\AppData\Local\python\mu
2018-09-05 08:15:23,302 - mu.logic:574(setup) INFO: Available modes: python, adafruit, microbit, debugger, pygamezero
2018-09-05 08:15:23,669 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:15:23,669 - mu.logic:623(restore_session) INFO: Restoring session from: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:15:23,669 - mu.logic:624(restore_session) DEBUG: {'theme': 'day', 'mode': 'microbit', 'paths': [], 'envars': [], 'minify': False, 'microbit_runtime': ''}
2018-09-05 08:15:23,669 - mu.logic:645(restore_session) INFO: Loaded files.
2018-09-05 08:15:23,669 - mu.logic:649(restore_session) INFO: User defined environment variables: []
2018-09-05 08:15:23,669 - mu.logic:653(restore_session) INFO: Minify scripts on micro:bit? False
2018-09-05 08:15:24,044 - mu.logic:671(restore_session) INFO: Starting with blank file.
2018-09-05 08:15:24,060 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:26:58,715 - root:112(run) INFO:
-----------------
Starting Mu 1.0.0
2018-09-05 08:26:58,715 - root:113(run) INFO: uname_result(system='Windows', node='MyDELL', release='8.1', version='6.3.9600', machine='AMD64', processor='Intel64 Family 6 Model 60 Stepping 3, GenuineIntel')
2018-09-05 08:26:58,715 - root:114(run) INFO: Python path: ['C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\Python\\python36.zip', 'C:\\Program Files\\Mu\\Python', 'C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\pkgs\\IPython\\extensions']
2018-09-05 08:26:58,821 - mu.logic:540(__init__) INFO: Setting up editor.
2018-09-05 08:26:58,822 - mu.logic:558(__init__) INFO: Settings path: C:\Users\MIROSL~1\AppData\Local\python\mu\settings.json
2018-09-05 08:26:58,822 - mu.logic:559(__init__) INFO: Session path: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:26:58,822 - mu.logic:560(__init__) INFO: Log directory: C:\Users\MIROSL~1\AppData\Local\python\mu\Logs
2018-09-05 08:26:58,822 - mu.logic:561(__init__) INFO: Data directory: C:\Users\MIROSL~1\AppData\Local\python\mu
2018-09-05 08:26:58,843 - mu.logic:574(setup) INFO: Available modes: python, adafruit, microbit, debugger, pygamezero
2018-09-05 08:26:59,224 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:26:59,224 - mu.logic:623(restore_session) INFO: Restoring session from: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:26:59,224 - mu.logic:624(restore_session) DEBUG: {'theme': 'day', 'mode': 'microbit', 'paths': [], 'envars': [], 'minify': False, 'microbit_runtime': ''}
2018-09-05 08:26:59,224 - mu.logic:645(restore_session) INFO: Loaded files.
2018-09-05 08:26:59,224 - mu.logic:649(restore_session) INFO: User defined environment variables: []
2018-09-05 08:26:59,224 - mu.logic:653(restore_session) INFO: Minify scripts on micro:bit? False
2018-09-05 08:26:59,597 - mu.logic:671(restore_session) INFO: Starting with blank file.
2018-09-05 08:26:59,612 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:27:18,831 - root:112(run) INFO:
-----------------
Starting Mu 1.0.0
2018-09-05 08:27:18,831 - root:113(run) INFO: uname_result(system='Windows', node='MyDELL', release='8.1', version='6.3.9600', machine='AMD64', processor='Intel64 Family 6 Model 60 Stepping 3, GenuineIntel')
2018-09-05 08:27:18,831 - root:114(run) INFO: Python path: ['C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\Python\\python36.zip', 'C:\\Program Files\\Mu\\Python', 'C:\\Program Files\\Mu\\pkgs', 'C:\\Program Files\\Mu\\pkgs\\IPython\\extensions']
2018-09-05 08:27:18,940 - mu.logic:540(__init__) INFO: Setting up editor.
2018-09-05 08:27:18,941 - mu.logic:558(__init__) INFO: Settings path: C:\Users\MIROSL~1\AppData\Local\python\mu\settings.json
2018-09-05 08:27:18,941 - mu.logic:559(__init__) INFO: Session path: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:27:18,941 - mu.logic:560(__init__) INFO: Log directory: C:\Users\MIROSL~1\AppData\Local\python\mu\Logs
2018-09-05 08:27:18,941 - mu.logic:561(__init__) INFO: Data directory: C:\Users\MIROSL~1\AppData\Local\python\mu
2018-09-05 08:27:18,963 - mu.logic:574(setup) INFO: Available modes: python, adafruit, microbit, debugger, pygamezero
2018-09-05 08:27:19,355 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:27:19,355 - mu.logic:623(restore_session) INFO: Restoring session from: C:\Users\MIROSL~1\AppData\Local\python\mu\session.json
2018-09-05 08:27:19,355 - mu.logic:624(restore_session) DEBUG: {'theme': 'day', 'mode': 'microbit', 'paths': [], 'envars': [], 'minify': False, 'microbit_runtime': ''}
2018-09-05 08:27:19,355 - mu.logic:645(restore_session) INFO: Loaded files.
2018-09-05 08:27:19,355 - mu.logic:649(restore_session) INFO: User defined environment variables: []
2018-09-05 08:27:19,355 - mu.logic:653(restore_session) INFO: Minify scripts on micro:bit? False
2018-09-05 08:27:19,724 - mu.logic:671(restore_session) INFO: Starting with blank file.
2018-09-05 08:27:19,739 - mu.logic:1110(change_mode) INFO: Workspace directory: C:\Users\Miroslav štandera\mu_code
2018-09-05 08:27:21,172 - mu.logic:1037(show_admin) INFO: Showing logs from C:\Users\MIROSL~1\AppData\Local\python\mu\Logs\mu.log
Štanderovi, Nový Bor
Dne 05. 9.. 2018 v 08:26 uživatel Nicholas Tollervey <[email protected]> napsal(a):
@standera if you copy and paste the log file after Mu crashes (see my previous instructions above), we'll be able to confirm your hunch about non ASCII characters in the account name. ;-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Hi @standera, Thanks for the log. Sorry for the barrage of questions, but this will help us isolate what the problem may be. I can see from the logs that you started the Mu several times during the session this log file covers. Can you confirm that Mu was crashing in the way you state during this session? I think your answer will be "yes" and I find it puzzling there's no stack trace or debug information. We've setup Mu so that if it ever crashes, then it should log exactly what went wrong. However, the lack of evidence for this crash report in the log (hence my check/confirmation that you actually observed a crash), suggests that it wasn't so much Mu that crashed, as Python itself (which Mu is written in) which crashed -- if you see what I mean. In any case, I believe your suggestion of non-ASCII in the save path might be the problem. I guess we'll start there and try to recreate the problem. Once we can observe the problem we can write a test to recreate it, then fix Mu so it no longer crashes (or change Mu so it no longer crashes Python). Thanks for your support! N. |
|
@standera Unfortunately I can't see a screenshot in your earlier post, so it looks like Github's process has dropped it. Can you try adding directly from the GH web interface, please? I'm still unsure whether you're getting a Windows fatal error -- in which case we probably won't get anything in the logs -- or some other error. |
|
No problem you do not bother me. I would like to help as far as I am able to follow.
I can see from the logs that you started the Mu several times during the session this log file covers. Can you confirm that Mu was crashing in the way you state during this session?
I
Indeed I can confirm YES.
Štanderovi, Nový Bor
Dne 05. 9.. 2018 v 09:52 uživatel Nicholas Tollervey <[email protected]> napsal(a):
Hi @standera,
Thanks for the log. Sorry for the barrage of questions, but this will help us isolate what the problem may be.
I can see from the logs that you started the Mu several times during the session this log file covers. Can you confirm that Mu was crashing in the way you state during this session?
I think your answer will be "yes" and I find it puzzling there's no stack trace or debug information. We've setup Mu so that if it ever crashes, then it should log exactly what went wrong. However, the lack of evidence for this crash report in the log (hence my check/confirmation that you actually observed a crash), suggests that it wasn't so much Mu that crashed, as Python itself (which Mu is written in) which crashed -- if you see what I mean.
In any case, I believe your suggestion of non-ASCII in the save path might be the problem. I guess we'll start there and try to recreate the problem. Once we can observe the problem we can write a test to recreate it, then fix Mu so it no longer crashes (or change Mu so it no longer crashes Python).
Thanks for your support!
N.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
|
|
The image should be there. I have just uploaded it.
Štanderovi, Nový Bor
Dne 05. 9.. 2018 v 09:56 uživatel Tim Golden <[email protected]> napsal(a):
@standera Unfortunately I can't see a screenshot in your earlier post, so it looks like Github's process has dropped it. Can you try adding directly from the GH web interface, please? I'm still unsure whether you're getting a Windows fatal error -- in which case we probably won't get anything in the logs -- or some other error.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@standera Thanks. Honestly, this is going to be tricky to debug. I don't think it's as straightforward as the fact of your having non-ASCII characters, although that's always a suspect. We have at least one user running in a Chinese locale where every character is non-ASCII. Are you in a position to run a development version of Mu? ie by creating a virtual environment and using pip to install the current version? If you don't know what I'm talking about, that's fine: I'm just trying to get a different angle on the problem and to narrow down exactly what's causing the crash. |
|
Sadly this is an unknown territory to me.
Štanderovi, Nový Bor
Dne 05. 9.. 2018 v 10:06 uživatel Tim Golden <[email protected]> napsal(a):
@standera Thanks. Honestly, this is going to be tricky to debug. I don't think it's as straightforward as the fact of your having non-ASCII characters, although that's always a suspect. We have at least one user running in a Chinese locale where every character is non-ASCII.
Are you in a position to run a development version of Mu? ie by creating a virtual environment and using pip to install the current version? If you don't know what I'm talking about, that's fine: I'm just trying to get a different angle on the problem and to narrow down exactly what's causing the crash.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Just to give it a quick test, I tried to create a folder with the settings.json: {
"workspace": "C:\\Users\\microbit-carlos\\Miroslav štandera"
}And Mu had issues decoding that path printing |
|
(sigh: I don't understand github's email ingest) Thanks for that, Carlos. Whether or not that's the current issue, we should definitely be able to fix that. I can't get to it now but if someone hasn't then I'll pick it up late |
|
One of my students is having a problem that sounds like this. |
|
Thanks again for the update @standera. There has been a few updates to better support Unicode since the last release, would you be able to try Mu from the master branch and see if that still causes the crash? |
|
Hello Carlos,
I would like to but I am not familiar with Github at all. So if there is a standard installation program (for Windows) just send me a link and I will try.
Sorry for my ignorance.
… 3. 9. 2020 v 22:01, Carlos Pereira Atencio ***@***.***>:
Thanks again for the update @standera <https://github.com/standera>. There has been a few updates to better support Unicode since the last release, would you be able to try Mu from the master branch and see if that still causes the crash?
https://mu.readthedocs.io/en/latest/#quickstart <https://mu.readthedocs.io/en/latest/#quickstart>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#635 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLLCLDW23QZY43UX3I2AZLSD7Y3PANCNFSM4FTCPJEA>.
|
|
Hi @standera, You can download the (testing) latest Windows installer from the master branch here: http://mu-builds.s3-website.eu-west-2.amazonaws.com/?prefix=windows/ |
|
Hello,
sorry for being delayed. I tried the latest version (64bit) today. Still the some result. No way how to save the file. I am sending you two screen shots (see the attached files) to better illustrate the problem (unfortunately only Czech language).
The text bellow is a report taken from the standard windows-crashing program. It may help as well. By the way hitting the help button in Mu leads to nowhere (a small bug).
Podpis problému:
Název události problému: APPCRASH
Název aplikace: pythonw.exe
Verze aplikace: 3.6.3150.1013
Časové razítko aplikace: 59d3d3a5
Název chybného modulu: StackHash_fe12
Verze chybného modulu: 6.3.9600.19678
Časové razítko chybného modulu: 5e82c88a
Kód výjimky: c0000374
Posun výjimky: PCH_A2_FROM_ntdll+0x0000000000090CBA
Verze operačního systému: 6.3.9600.2.0.0.256.48
ID národního prostředí: 1029
Další informace 1: fe12
Další informace 2: fe1200a364f573139d2ff1ee6fb7ada3
Další informace 3: 5123
Další informace 4: 512308f6725192308933b70c65d0b4f5
Miroslav Štandera, Nový Bor
Dne 25. září 2020 15:17 uživatel Carlos Pereira Atencio <[email protected]> napsal(a):
Hi @standera,
You can download the (testing) latest Windows installer from the master branch here: http://mu-builds.s3-website.eu-west-2.amazonaws.com/?prefix=windows/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Hi @standera, it's my first look at this bug. I can see that you intended to include attached screenshots in your last email-reply to this thread. However, it seems that the attachments are not included when send as email, could you login to Github and upload the screenshots? (if you still have them... perhaps they are saved in your mailbox for "Sent mail") |
|
I have the same problem. I have try to install the latest version (1.1.0 beta 3) on windows 10 (64 bits) several times |
|
Hi @MichelleStella, |
of course : |
|
Thanks for the logs @MichelleStella! If Mu does close down or crash, what do you see, when does it crash? |
|
@standera we've done a new release since you last tested this issue, would you be able to install the latest release and try again? Thank you again for all your testing! |
Weird.. Here is the video of what happened (sorry for the background noise) https://www.youtube.com/watch?v=3ARHA6teusI&ab_channel=MichelleStella |
|
This feels like a bug in Python or PyQt (the error reported is that Python has stopped responding - and this is backed up by evidence because Python hasn't written anything to the log file to indicate the problem it encountered). I wonder if there's a core dump somewhere (clutching at straws here) that we can examine to figure out the underlying problem? There's certainly nothing visible in the Mu layer of the application (hence my thought about the problem being in the Python or Qt layer). I also notice that the error happens when the OS's file dialog is displayed / triggered by Python... again, not a Mu thing per-se... Mu is just using the standard PyQt method to trigger the dialog. |
|
A further thought.... perhaps it's something in PyQt and it won't be fixed until we update to, say, latest PyQt5 or the new PyQt6. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Windows 8, last version of Mu Editor. I have tried reinstalling couple of times (one / all users) but no success. Actually there is no way how to solve it, or is it?
The text was updated successfully, but these errors were encountered: