I am using pydev through Aptana Studio 3 on a mac. Shortly after opening up Aptana, my computer heats way up, the fans go full power, and Aptana uses over 100% cpu even when it's not doing anything. I also have pydev on eclipse, but this spike doesn't occur. Has anyone else seen this? Is there any way to stop it?
The only way to really know what's going on would be connecting jvisualvm (or some profiler or debugger) to your process to see what's going on (and then report an issue). On jvisualvm you can get a dump with the current processes, which may be enough already if you can say which is the thread that's running.
Note that the title should probably be 'aptana studio 3 massive cpu usage' if you're able to reproduce it there but not in pydev...
Related
I have a PyQt application that occasionally will crash due to memory issues with the error shown below
The instruction at 0X00007FFC450FA07 reference memory at 0X0000000000000048. The memory could not be read.
I personally have not been able to reproduce this error in any way. It has happened on the computer's of a few people I work with while running my application. I have looked and see a lot of questions for languages like C# or C++, and it seems to be a pointer issue. Since I am using Python though, these questions and solutions are not very relevant since Python does not use pointers.
Seen here: C# example question the problem here is a long running thread. I do use threading in my application so I have been looking there. I have ran my application many times with the task manager open to monitor threads and have not seen any problems. All threads seem to close. If there is a better way to monitor this please let me know.
I am using PyCharm and my Python version is 3.9. I am also using Pyinstaller to create an executable version of the application. I have ran the program using the command line, launching the executable, and also directly through PyCharm and have not been able to see the error at all or debug it.
Is it possible this is happening due to bit related issues? Meaning that I am compiling my code using a 32-bit version of Python, could some computers have a problem with that? Would compiling with a 64 bit version possibly solve this?
I'm going to make this question as succinct and to the point as possible. I have a jupyter notebook that worked perfectly yesterday. Today, my windows 10 machine demanded an update and after updating, the jupyter notebook now cannot run. I can import libraries and define functions, but when I actually go about using the libraries and functions for computations, the [*] denoting python is busy never goes away, meaning the code is stuck (or is super slow). Even after 20 minutes the first code cell is not carried out. Yesterday, this notebook would run all 40 (roughly) cells in seconds. I have no idea why this happened, where to start trouble shooting from, or who to turn to for support. Has anyone else encountered this issue?
Windows: 10 (Version: 1607, OS Build: 14393)
Python: Anaconda (Python 3.5)
Architecture: 64 bit
Jupyter Notebook File + Resorces: https://github.com/diggetybo/ICA-Attachments
Maybe the windows update meant well, but it created a lot of upheaval on my system. I had to reconfigure a lot of settings ranging from privacy to monitor display resolution. I believe some registry entries are different, although I typically don't look registry entries on a day to day basis. Some registry switcharoo is my best guess as to why Python suffered from the update.
Good news is I got it functional again by reinstalling anaconda. It was a time consuming and desperate approach to the problem. At someone's leisure, any technical explanations as to why this might have occurred could still be worth posting. I'm hoping I won't have to do this every windows update.
I'd like to exempt myself from user error, but I'm not sure whether others have this problem or not. Please share any similar experiences in the comments.
Thanks for reading.
I'm a little bit puzzled here right now.
I have Win7 64bit with Python 3.4.3 and LabVIEW 2015 installed. Out of the blue the system became very slow and two problems in particular arose. I can not use Idle any more (IDLE's subprocess didn't make connection...) and LabView is sort of reacting, but to slow to be used and crashing all the time. Firewall and Antivirus are turned of and I'm totally out of idea what could cause this. The system defnetily has enough power for what I'm doing and already successfully did:
Fujistsu c740 workstation
Xeon 6 core E5-1650 v3
32Gb ram
SSD
etc
I installed Tortoise svn and updated git, except that I did not install anything new or change any settings. After some googleing I found out that in msconfig->Boot/>Advanced Options-> Number of Processors was set to 1. I changed it to 12, but this did not help.
Any help would be very appreciated!
Cheers
When looking for an area to investigate for a murky problem, I typically start with Process Explorer, which is a developer's Task Manager.
In addition to viewing the overall CPU/Memory/Disk/IO load, you can also slice those measurements by individual processes. The tool even goes further to show all of the threads in that process as well as their call stacks. In addition, it can find open DLL and file handles.
I seem to be getting a Runtime error whilst running my Python script in Blackmagic Fusion.
# "The application has requested the Runtime to terminate it in an unusual way".
This does not happen every time I run the script. It only seems to pop up when I feed the Python script a heavy workload, or if I run the Python script multiple times inside of the Blackmagic Fusion compositing software, without restarting the package. I thought this might be a memory leak, but when I check the CPU memory usage, it does not seem to flinch at all.
Does anyone have any idea what might be causing this, or at least a solution of how I might start to debug the script?
Many thanks.
if you know how to get runtime error, then run your script using pdb
Perhaps this'll help. It's apparently a common error with microsoft visual c++:
http://support.microsoft.com/kb/884538
I am running a stand-alone Python v3.2.2/Tkinter program on Windows, not calling any external libraries. Idle has been very helpful in reporting exceptions, and the program has been debugged to the point where none are reported. However, the python interpreter does occasionally crash at non-deterministic times - operations will run fine for a while and then suddenly hang. The crash triggers the standard Windows non-responding process dialog asking if I want to send a crash dump to Microsoft:
"pythonw.exe has encountered a problem and needs to close.
We are sorry for the inconvenience."
Crash reporting in Python says that the interpreter itself rarely crashes. My question is: no matter how many mistakes there are in a python script, is there any way it should in theory be able to crash the interpreter? Since there are no exceptions being reported and the crashes happen at random times, it's hard to narrow down. But if the interpreter is in theory supposed to be crash-proof, then something I'm doing is triggering a bug.
The code (a scrolling strip-chart demonstration) is posted at What is the best real time plotting widget for wxPython?. It has 3 buttons - Run, Stop, Reset. To cause a crash just press the buttons in random order for a minute or so. With no interaction, the demo will run forever without crashing.
Of course, the goal is for something like Python to never crash. Alas, we live in an imperfect world. A more useful question to ask, I think, is "What should I do if Python crashes?". If you want to help make a more perfect world, first make a quick search at the Python issue tracker to see if a similar problem has already been reported and possibly fixed in a newer or as yet unreleased version of Python. If not, see if you can find a way to reproduce the problem with clear directions about steps involved, what OS platform and version, what versions of Python and 3rd-party libraries, as applicable. Then open a new issue with all the details. Keep in mind that Python, like many open source projects, is an all-volunteer project so there can be no guarantee when or if the problem will be more deeply investigated or solved (most issues are resolved eventually) but you can be happy that you have done your part and likely saved someone (maybe many people) time and trouble. If you want other opinions before opening an issue, you could ask about it on the python-list mailing list/news group.
Python isn't indeed 100% crash proof, especially when you using external libraries, which TkInter is.
There is even page dedicated to it: http://wiki.python.org/moin/CrashingPython