Version lookup in RAWBInfo slows down system with big files
Posted: Tue May 21, 2013 12:20 am
Granted, i clicked on it by accident 
Still it brought up a really annoying behaviour
Steps to reproduce:
1) Find a really big file (I used a 560+ MB .iso file)
2) Mark the file and choose Icon/Information from the Workbench pull-down menu
3) Click on the "?" button right of the "Version:" text
4) See the system go down in speed and useability
CPU useage goes up to 100%, system is completely slowed down and will stay until the Version lookup has been finished (which will take AGES due to the CPU useage at 100%)
Not sure if it used to work that way (at least i remember to do such stupid things in earlier versions and it didn't slowed the whole system down, but one can't count on my memory)
Now to the real problem...one cannot cancel this in any way.
Activating the Information window brings up a busy clock with no further actions one can perform...i did a rebooot ultimately.
Maybe this can be changed to not use up all the CPU cycles, maybe there is something else that could be done (apart from telling me not to do this again?

Still it brought up a really annoying behaviour
Steps to reproduce:
1) Find a really big file (I used a 560+ MB .iso file)
2) Mark the file and choose Icon/Information from the Workbench pull-down menu
3) Click on the "?" button right of the "Version:" text
4) See the system go down in speed and useability

CPU useage goes up to 100%, system is completely slowed down and will stay until the Version lookup has been finished (which will take AGES due to the CPU useage at 100%)

Not sure if it used to work that way (at least i remember to do such stupid things in earlier versions and it didn't slowed the whole system down, but one can't count on my memory)

Now to the real problem...one cannot cancel this in any way.
Activating the Information window brings up a busy clock with no further actions one can perform...i did a rebooot ultimately.
Maybe this can be changed to not use up all the CPU cycles, maybe there is something else that could be done (apart from telling me not to do this again?
