PyCharm closes and sometimes macbook restarts while running my python script on it. The script runs for a while and suddenly I get the following error:
PyCharm quit unexpectedly
Problem details and system configuration:
How to solve this issue please? Thank you
PS: the error message is too long with details so I have just added the initial part which I think should be enough but I can add all of it if required.
Related
I have looked on the internet, and some people suggested updating my windows 11 to the latest build; however, it did not solve the problem. One person indicated that they could solve the issue by reinstalling the windows. I can't afford to perform a clean install. How can I solve this issue? I can't open PowerShell or terminal natively aside from vs-code. As soon as I try running windows Powershell this error shows up.
[
Sometimes when i open the msys2 mingw64 bit terminal an error is displayed in console:
Error: Could not fork child process: There are no available terminals (-1).
This error oqurues many time during the project time, but if i restart the laptop, there is no error.
Anyone who has facing simillar error?
I have seen this issue too, and it disappears after reboot.
Make sure you have run autorebase.bat in the msys64 folder.
So I'm trying to run my fuchsia emulator but I keep running into the same problem. I'm running on a Virtualbox VM of Ubuntu v20.04. I set up and built core.qemu-x64 according to the getting started instructions on fuchsia.dev website. However, whenever I run fx vdl start -N while in the fuchsia directory I just get "[info] Waiting for emulator to start..." which it repeats endlessly. Looking at the logs it shows the error message "Reading sdk version errored: No such file or directory (os error 2)". This seems like why the emulator is failing to start. Looking online it seems to be a problem with how this version of Ubuntu resolves certain imports.
Is there a way I can start the emulator that would tell me what file(s) this error is coming from so I can manually resolve it? Otherwise, is there another solution that could fix this issue?
Thank you for any input, please let me know if I can provide any additional information.
Below is a screenshot of the output:
Edit:
I tried fx qemu -kN and got this output but no change to the original start behaviour:
I also tried fx emu and got this output, still no change to the original start:
So I was able to resolve it eventually and first of all, I'd recommend increasing the allocated RAM of your VM. I went from 2GB to 7GB and I'm pretty sure that resolved part of it. Then continue with Marco's recommendations. The command fx qemu -N (or fx qemu -Nk if you have kvm enabled) seemed to do it for me. After I ran that I got another error message with a different command to run. Once I ran that new command and reran fx qemu -N it seemed to start working. Finally opening another terminal and starting fuchsia with fx vdl start -N made the emulator start up just fine. Thanks for the help everyone!
I am running QtCreator#4.6.1 based on Qt#5.11.0 on Arch Linux#4.16.12-1-ARCH
When starting QtCreator with an active cmake project, the program crashes immidiatley with a notification window titled "File Error". If I delete the folder <PATH>/.config/QtProject, it starts without problems.
Starting with qtcreator -noload Welcome I can see the a start of cmake server in the shell. No error output in the shell from where I called the project.
How can I debug that behaviour? I really would like to keep my previous projects/sessions and settings.
I just ran in the same problem. Removing ~/.config/QtProject/qtcreator/helpcollection.qhc fixed the problem.
Edit: fixed path, forgot "qtcreator"
In PyCharm, if I run a script in debug mode (with debug console on), then stop at a breakpoint, and try to type something into the console, I get:
MultipleInstanceError: Multiple incompatible subclass instances of PyDevTerminalInteractiveShell are being created.
Does anybody know what might be causing this and how to fix it?
For me, I had this issue when using ipdb in another terminal from the same code. I had ipdb present in file A, and a terminal with an ipython shell open running this code. I commented out the ipdb bits from file A and ran the debugger in pycharm and this error started up. When I closed the shell I had open in my terminal the error went away.