NOTICE: This forum is mostly an archive, though new posts are allowed. Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by XP SP3 x86, May 09, 2012, 01:30:12 PM
QuoteHowever, these were resolved, and they were NOT as you describe here.
Quote from: bitsum.support on May 10, 2012, 12:45:49 PMBTW, are you running the core engine as a service or normal application?
Quote from: edkiefer on May 11, 2012, 08:11:01 PMNo problem with v18.104.22.168 here with XP SP3 , just tested it an shuts down cleanly .
Quote from: Miroku4444 on May 12, 2012, 11:05:58 AMWell the latest fix(22.214.171.124) is now causing a start-up issue. Process Lasso is taking too long to boot up, and is preventing some of my other apps from starting. They all start up eventually, but a couple must wait for process lasso. One of them is my firewall, which might make me vulnerable while process lasso is starting up.
Quote from: Miroku4444 on May 12, 2012, 12:04:43 PMI fixed it, and it wasn't Process Lasso's Fault. During a Microsoft update the service ".NET Runtime Optimization Service v2.0.50727_X86" got re-enabled. It uses a process called mscorsvw.exe. This sucker slows my start-up like crazy. I disabled it and re-booted. Now everything starts up like normal. I guess i forgot to disable it after a microsoft update.
QuoteAll to hide just how slow and bloated .NET apps are.
Quote from: Miroku4444 on May 12, 2012, 02:02:59 PMMost are, but Paint.NET is awesome and not bloated at all.
Quote from: bitsum.support on May 12, 2012, 07:59:57 PMIf you turn on the view of DLLs in Process Lasso, then you can also tell by the DLLs that are loaded ..
Quote from: Hotrod on May 12, 2012, 08:39:47 PMHuh??? Where do I find that?
Quote from: bitsum.support on May 12, 2012, 12:44:24 PMIf you remember, when .NET was originally introduced it was so dog slow that Microsoft had to add all sorts of system services to help speed it up. Pre-load assemblies, pre-optimize, pre-compile MSIL to native code, etc.. All to hide just how slow and bloated .NET apps are. That particular service (the second one, NGEN), is described as: "NGen service allows the developer to defer the installation and update of native images to periods when the computer is idle." .. At least, that's how it is described by a person here: http://social.msdn.microsoft.com/Forums/eu/netfxsetup/thread/4dd266e6-a93b-4195-81f8-109312004f4f
QuoteSo those that run into issue wait a few days or you could do as in link above and force compile , last resort would be set service to manual or disable but I think if you have any apps you will lose the optimization if service is not able to run .
Quote from: KestutisS on October 06, 2012, 10:29:16 AMHi, to all... this may be a regression in 126.96.36.199 or a new issue -- on system Shutdown Process Lasso may try to start something as there are message boxes with failed initialization because of shutdown displayed: I tried to shutdown my PC several minutes ago, and the Icon in the tray was 3xRED (as it is described in the beginning of this thread), but the process did not terminate for about a minute. During that time I've got 4 message boxes with information that .DLL failed to initialize because system is going Shutdown (processgovernor.exe). (The text may be inexact).
QuoteMy thought is that processgovernor or whatever should not complain about shutdown.