I have a strange issue with Picaxe Editor 184.108.40.206: the longer the program is left open, the more sluggish it gets - finally reaching a stage where it can no longer keep up with key strokes.
A restart cures it for a while. The problem seems to occur with 'time' rather than 'usage'; i.e. I can come back to my PC after a long idle period, to find it in that state. It does not die completely; it just gets slower and slower. Actually, if you leave it long enough, it does lock up completely.
I have not tried to reproduce it with a simpler 'workspace' than I am currently using, so I'm reporting it at this stage, purely because it might illicit some 'me too' responses - I appreciate I have probably not provided enough information to solve it.
Looking at the PicaxeEditor.exe process in Task Manager (with the symptoms present), I notice the following :
- Near constant 25+% CPU usage (the PC has a 4core processor - but reducing the no. available to PicaxeEditor doesn't alter the percentage ... (it's not a straight-forward cpu-bound loop, which would give 100% on 1 CPU)
- It has the largest Working Set of any process on the system @ 510,000K and the largest amount of Physical Memory @ 160,000K
- It has the largest no. of threads @ 31
- It has the largest no. of User Objects @ 550
- It is in the top 10 'GDI Objects' @ 484
- I/O other is the most startling: 300,000,000 operations, resulting in 6,000,000,000bytes of data (6 GIGA bytes!) - amassed while using 1.5hrs CPU time.
Using SysInternals Process Explorer, I can see that all the CPU activity is taking place in a single thread (PicaxeEdit+0x3da3d0). The Stack for that thread shows details such as:
(if that helps at all).
Please advise a diagnostic strategy