Revision history [back]

It's been a while since I played with the SDK, but it used to take around 10-20s from clicking run to having the program running in the emulator (that was during SFOS 2.0ish), now even rather simple program takes about 2 minutes to show up. Is it the intel bugs that were supposed to impact virtualization, or some misconfig on my part? (didn't really cahnge anything and just installed the default build targets, so doubt it)

It's been a while since I played with the SDK, but it used to take around 10-20s from clicking run to having the program running in the emulator (that was during SFOS 2.0ish), now even rather simple program takes about 2 minutes to show up. Is it the intel bugs that were supposed to impact virtualization, or some misconfig on my part? (didn't really cahnge change anything and just installed the default build targets, so doubt it)

It's been a while since I played with the SDK, but it used to take around 10-20s from clicking run to having the program running in the emulator (that was during SFOS 2.0ish), now even rather simple program takes about 2 minutes to show up. Is it the intel bugs that were supposed to impact virtualization, or some misconfig on my part? (didn't really change anything and just installed the default build targets, so doubt it)it)
EDIT: btw this is on win10, maybe there was no regression on linux, no idea

It's been a while since I played with the SDK, but it used to take around 10-20s from clicking run to having the program running in the emulator (that was during SFOS 2.0ish), now even rather simple program takes about 2 minutes to show up. Is it the intel bugs that were supposed to impact virtualization, or some misconfig on my part? (didn't really change anything and just installed the default build targets, so doubt it)
EDIT: btw this is on win10, maybe there was no regression on linux, no idea

It's been a while since I played with the SDK, but it used to take around 10-20s from clicking run to having the program running in the emulator (that was during SFOS 2.0ish), now even rather simple program takes about 2 minutes to show up. Is it the intel bugs that were supposed to impact virtualization, or some misconfig on my part? (didn't really change anything and just installed the default build targets, so doubt it)
EDIT: btw this is on win10, maybe there was no regression on linux, no idea

It's been a while since I played with the SDK, but it used to take around 10-20s from clicking run to having the program running in the emulator (that was during SFOS 2.0ish), now even rather simple program takes about 2 minutes to show up. Is it the intel bugs that were supposed to impact virtualization, or some misconfig on my part? (didn't really change anything and just installed the default build targets, so doubt it)
EDIT: btw this is on win10, maybe there was no regression on linux, no idea

It's been a while since I played with the SDK, but it used to take around 10-20s from clicking run to having the program running in the emulator (that was during SFOS 2.0ish), now even rather simple program takes about 2 minutes to show up. Is it the intel bugs that were supposed to impact virtualization, or some misconfig on my part? (didn't really change anything and just installed the default build targets, so doubt it)
EDIT: btw this is on win10, maybe there was no regression on linux, no idea

EDIT: I think this was fixed in 3.1, 3.1 (or maybe even 3.0, not sure when that was released), or at least right now deploying as RPM to the emulator is taking 15-20 seconds and the hangups are gone, haven't tested yet the 3.2 that was just released, I guess this can be closed unless people still are experiencing this issue

It's been a while since I played with the SDK, but it used to take around 10-20s from clicking run to having the program running in the emulator (that was during SFOS 2.0ish), now even rather simple program takes about 2 minutes to show up. Is it the intel bugs that were supposed to impact virtualization, or some misconfig on my part? (didn't really change anything and just installed the default build targets, so doubt it)
EDIT: btw this is on win10, maybe there was no regression on linux, no idea

EDIT: I think this was fixed in 3.1 (or maybe even 3.0, not sure when that was released), (yup, checked the release notes, under fixed: SDK on Windows: build/run taking a lot longer than it used to, closing), or at least right now deploying as RPM to the emulator is taking 15-20 seconds and the hangups are gone, haven't tested yet the 3.2 that was just released, I guess this can be closed unless people still are experiencing this issue