06-08-2015 01:42 PM
But you didn't mention if it ever worked well on the copied code...
06-08-2015 01:43 PM
40% CPU and 280 megs of RAM.
06-08-2015 01:44 PM
Hey, it's okay - sometimes detectives have to nudge the witness to see if they can recall more details. 🙂
06-08-2015 02:04 PM
Ok... i think i lied. After '11 minutes' it stopped searching, and looks that found what i'm looking for. But it takes very, very, very long time - really about 10 minutes.
06-08-2015 02:12 PM
@kacperek wrote:
Ok... i think i lied. After '11 minutes' it stopped searching, and looks that found what i'm looking for. But it takes very, very, very long time - really about 10 minutes.
LOL - no worries. There's still something not right here. It shouldn't take that long. (Personally I thought the ten minutes you took was way enough time to determine if it wasn't responding.) The library being searched was copied to the new machine from the original one?
06-08-2015 02:36 PM
OK 🙂 Library was copied directly. I'll check how it works on primary machine tomorrow but i'm afraid it's not. Good news that it takes ages but works. So maybe i can live with this. Thanks 🙂
06-08-2015 02:59 PM
Keep us updated, especially if you did something to fix it. Not only am I very curious, but it would be VERY helpful to someone who might have the same kind of problem in the future. 🙂
06-08-2015 03:02 PM
Have you looked at that VI file on disk to see how large it is? I ran into a similar problem once, I remember it was because someone had saved the .VI with a very large amount of data as the default value in a graph. As a result, the VI file was unusually big (maybe a couple MB), and it took a long time to search that VI for text because LabVIEW has to search through all that data. The fix was easy of course, just change the graph's default value to empty.
06-08-2015 03:03 PM
Of course, this is the idea of forum 🙂
06-08-2015 03:08 PM
Soooo problem solved thanks to garrettmarsh ! I have quite big string array (ugly code due to little time, i'll change this). After remove this array searching takes half a second. Thank you guys for a help.