Hi @defragster,
Thanks for the reply.
I had actually started using the all in one to update from a previous beta of 1.53 that was installed in arduino and also had the problem.
So I thought I would delete the original arduino app and re-install so I could make some timings of the issue compared to the default.
So with 6 file editors:
Starting Arduino is still pretty slow and takes around 10 seconds, starting teensyduino takes around 19 seconds.
File menu popping down in arduino is 0.5 seconds, file menu in teensyduino takes 8.5 seconds.
Sketch menu popping down in arduino is instant, teensyduino around 0.5 seconds.
Other menus are fine in both.
In both arduino and teensyduino once the file menu has had this slow behaviour as long as you stay on the same editor window it then works quickly, change to another editor window and it is slow the next time.
So I'm guessing it is something to do with the number of examples rather than the teensy stuff, I bet if I had another board with the same number of examples I would see a similar thing.
Edit:
So I ran the Instruments profiler on it to see what is going on, maybe doesn't look like a disk issue.
7.66 s 100.0% 1.00 ms Java_sun_lwawt_macosx_LWCToolkit_doAWTRunLoopImpl
So some Java toolkits run loop, with majority of time here:
5.07 s 66.2% 129.00 ms CFSetContainsValue
So it looks like it is some dodgy code looking stuff up in a set.
I also ran a filesystem profile and there is no disk access at all in this period.
So looking like an Arduino problem based on number of examples and some dodgy code!
Thanks for the reply.
I had actually started using the all in one to update from a previous beta of 1.53 that was installed in arduino and also had the problem.
So I thought I would delete the original arduino app and re-install so I could make some timings of the issue compared to the default.
So with 6 file editors:
Starting Arduino is still pretty slow and takes around 10 seconds, starting teensyduino takes around 19 seconds.
File menu popping down in arduino is 0.5 seconds, file menu in teensyduino takes 8.5 seconds.
Sketch menu popping down in arduino is instant, teensyduino around 0.5 seconds.
Other menus are fine in both.
In both arduino and teensyduino once the file menu has had this slow behaviour as long as you stay on the same editor window it then works quickly, change to another editor window and it is slow the next time.
So I'm guessing it is something to do with the number of examples rather than the teensy stuff, I bet if I had another board with the same number of examples I would see a similar thing.
Edit:
So I ran the Instruments profiler on it to see what is going on, maybe doesn't look like a disk issue.
7.66 s 100.0% 1.00 ms Java_sun_lwawt_macosx_LWCToolkit_doAWTRunLoopImpl
So some Java toolkits run loop, with majority of time here:
5.07 s 66.2% 129.00 ms CFSetContainsValue
So it looks like it is some dodgy code looking stuff up in a set.
I also ran a filesystem profile and there is no disk access at all in this period.
So looking like an Arduino problem based on number of examples and some dodgy code!
Last edited: