Opened 8 years ago

Closed 8 years ago

#934 closed defect (worksforme)

to much output blocks Padre

Reported by: kreetrapper Owned by:
Priority: major Milestone:
Component: editor Version: 0.56
Keywords: Cc:


When you run a script that outputs too many lines in Padre, the IDE almost freezes. It hogs almost the complete CPU (98% according to top) and, depending on how large the output is, takes awfully long to finish. It could even be that it never finishes at all. Outputting 9000 lines, blocked Padre for about 33 seconds. With 90,000 it was still running after more than 20 minutes. It is, however, still possible to close Padre during this, so it's not completely blocked.

Reproduce the problem with a simple script like
for (1..9000) { print "hello world\n"; }

Change History (2)

comment:1 Changed 8 years ago by waxhead

Maybe related to the fix from #756 which required a fix to Wx::Perl::ProcessStream? ( or something like that ).

Just waiting to upgrade Padre to 0.60 to see if this is still a problem.

comment:2 Changed 8 years ago by waxhead

  • Resolution set to worksforme
  • Status changed from new to closed

Well after getting Padre upgraded to 0.60 on my Vista machine I ran the exact script, hit F5 to run it and it ran...

I then moved around Padre, opened a few folders in the Directory Tree view, opened a file closed a file.. watched the output some more.

All of this was a little slow, but reasonable, however it might have something to do with the specs of the hardware of this machine, not the the least being a quad core running something like 2.33GHz and lots of ram.. 4gig.

I'm not sure what's to be expected here, but I didn't find the slowness, or the cpu usage here.. looking at the cpu monitor here I see one core is doing plenty of work and it's sitting about 60-80%.

I am also able to stop the running perl script when I need to as well.

I think it could be in part, improvements to Wx::Perl::ProcessStream? and hardware.

Suggest that you upgrade Padre to the latest - being 0.60, upgrade the required modules as needed and try this again for yourself. If you still see things aren't too good then post details about hardware with the ticket and someone might be able to offer something a little more than I can at the moment.

Thanks for taking the time to fill out the ticket though.

Note: See TracTickets for help on using tickets.