I was hesitant to issue this interim update because I had not diagnosed all the new minidumps sent to me. That new functionality is definitely helpful, and will be more helpful as I refine it. Sadly, it isn't yet as helpful as I'd hoped, though is definitely a good clue and gives me an idea of where the problem occurred.Consider it yet another 'nightly build'. I probably did NOT get to evaluating your minidump submission or crash report, I haven't gotten to them yet and am also attempting some more general fixes to improve safety conditions. Most...
Monday, 21 February 2011
During testing I've noticed some undesirable behavior of the Keep Running feature under certain scenarios. Under one scenario, it kept launching the process over and over due to a misconfiguration caused by the new beta automated updater.One, in the next beta build process instances will be counted by base names. The path names don't have to match up, as they previously did. I can provide an option if anyone needs the old behavior. That means if you want to keep c:\windows\system32\notepad.exe running, a copy running in c:\test\notepad.exe will...
Those who have used the auto-updater have had their manifests changed, potentially causing errata in the latest betas. So, do a proper update. Yes, this issue was fixed once before, but the SFX archives used to silently update the product were being updated instead of recreated, causing the bug to persist.Due to this possible manifest and configuration mismatch, to avoid certain bugs you need to run a proper update with the installer. Remember, the beta quick updater is still experimental. I've already seen problems in QA testing in XP of the latest...
Sunday, 20 February 2011
I didn't announce this release because I passed out shortly afterwards. It is only about 95% of what I wanted anyway. Still, it represents a large change. I did come across one snafu, and that is updating the self-updater when the self-updater is doing the update. There are several ways to work around the problem, but for now I'm not updating it. Therefore, keep that in mind ;o. Of course, if the self-updater didn't work ok, then I assume you got the full installer and now have the new quick updater that will hopefully do better in the future.All...
Thursday, 17 February 2011
The new auto-updater in this beta series has been fixed up and overhauled with a new status bar and working cancel and restart capabilities. It auto-starts and auto-terminates, of course, but still sometimes that is needed. It also fixes problems with previous editions.This will be available in v4.09.26 beta, or possibly sooner as a stand-alone download. Remember, if used internally, you will be using the LAST rendition of the auto-updater for...
Wednesday, 16 February 2011
I've had someone ask how to submit a minidump. Well, you get to do that when/if the crash happens. When/if Process Lasso crashes, you now see a message box telling you that a minidump was generated, and asking if you would like to open that folder. This makes it easy for you to ZIP and submit minidumps to Bitsum Technologies. Using this minidump, we can hopefully get a better idea of the cause or location of the crash. It remains to be seen just how useful they'll be, but we'll see. Be sure to ZIP or RAR before you send, as they can be quite...
Tuesday, 15 February 2011
The official release of v4.09.25 has occurred.As I mentioned, this should take care of some of those GUI crashes, and the updater crash for the GUI, as some debug output was marked the wrong type, causing a virtual memory read error on some systems, x32 systems being the most affected. This did not exist in the last final because there was not this debug output the...
I found the cause of the crash in the newer code. This would manifest as a seemingly random crash of the GUI (background update check), or when you did an update check -- but only when an update was available. The cause? A simple typo/mistake with some debug output (type defined wrong, causing failure under some cases). This will likely solve many/most cases of unknown GUI crashes in the most recent beta series.This crash fix, amongst other fixes, will be available in v4.09.25 be...
Note to some Vista+ users of the last automated BETA(only) update: It may have lowered your UAC level of Process Lasso, so you may need to reconfigure that and end up re-running the installer to be safe and sure. I discovered this bug in the beta series and wanted to convey it.I have fixed the problem with it saying 'Can not Terminate all instance of Process Lasso' and am going to be issuing v4.09.25 beta soon. This is getting closer and closer to 'there'.I've also got FULL minidump support. In the unfortunate case of a crash, no more lame non-working...
Monday, 14 February 2011
What kind of holiday is this? Women get whatever they want, usually silly absurd things, and men get screwed (if they are lucky). Oh well, back to work after this torturous holiday. I soon will have a new beta with the aforementioned minidump support and improved auto updater (remember, improvements lag a build behind). More improvements coming, of course, all over...
Sunday, 13 February 2011
Ok, in my short-term haste I've made my own life harder by not using minidumps. That changes now. For all FUTURE builds when a crash occurs in Process Lasso a minidump will be generated. You can then send me that minidump and I'll have a much better idea of what just happened, and be able to fix it instead of willy-nilly around with code review or replication.Now, this hasn't been just flicking a switch - We've had to code proper support within the application and within the build and release framework. In the long run, it will save considerable...
In some prior betas there was an extra zombie instance of the governor at boot, depending on the speed of the boot. This fixes that problem and updates the Russian translation (an important update given its rarity and direct RC translation), amongst other languages.You can try the automated updater now too. I haven't even tested it myself in anything but Win7 x64, so that's where it is - but it should be fine (famous last words). In a worst case scenario, use the proper installer.Enj...
As described this stand-alone updater 'just does it'. You don't even need to click Start, it auto starts and auto closes. It still needs refinement. I am adding a Status bar to indicate connection status, hence the extra space left at the bottom. None-the-less here is a screenshot showing it downloading the update successfully and about to extract and self-terminate (I had to be quick with the screenshot, lol).The cool thing is that I can put this...
Saturday, 12 February 2011
For the curious, and although there are other extensions as well, if you want to see just how fast the update is (and I actually slowed it down because it was faster than the disk), then open the command prompt. Go to the PL installation directory. Then run QuickUpgrade.exe. This will upgrade your copy (to the current version). It still needs refinement, some tweaks and fixes, etc.. but there it ...
This new beta version has the long anticipated, and rumored to not exist, auto-update mechanism. It is revamped. Depending on your download speed it can take as little as 2 seconds to update your installation. No fuss, no mess. It just does it. For now, I've just got a button 'Try automatic upgrade'. In the future, I'll use this as the primary mechanism, once it is well tested, and turns out to be suited for the job. So, the NEXT update you'll get to actually try out this mechanism. I think it should work well. It self-downloads, which may be the...
I'm proud to announce the new silent, automatic updater. It will be extended as time goes on, but I am about to publish the coolest little utility. Run it, and PL is updated. In future builds of Process Lasso, it will be run by Process Lasso for automatic updates. It is nice to see it up and going ;)The allowance of this feature is actually the culmination of significant planning. Now, not every update will be silently and automatically updateable, but I'd guess 99% will ...
Friday, 11 February 2011
The new automated updater is an independent EXE with independent resources. Once run, it does this simple task:Download appropriate update for version XShut down Process LassoReplace necessary filesRestart Process LassoIt may not work for everyone, but will for many. It will do all the above without user intervention, if they've selected to that.This will be available in an upcoming beta soon. You WILL be able to try it out on the next beta upgrade because I'll provide a direct link to this new updater.What's even better is that we are making this...
Wednesday, 9 February 2011
I've already moved on to several new features, including properly checking the new 'Exclude from ProBalance' feature found in the LOG right-click context menu. That's right, you may not have noticed it -- but there it is. You can exclude a process no longer running without having to go through all those dialogs. I may expand this to simply include the entire standard process context menu, time will tell.Since I've got a relatively good build out there, I'm going to stick with it and bunch the next batch of enhancements and fixes together.In the...
Tuesday, 8 February 2011
I was notified by a tester that the default power schemes did not work in v4.09.22 beta, so wanted to issue a quick fix for that. I also wanted to issue a new build before I embarked on larger changes headed towards the completion of v4.1. I have shuffled the deck a bit, some sudden and wonderful things are comi...
After considerable more digging than I anticipated, I have released a new BETA, restoring public access to this new beta series. I am working hard here to get this finished and v4.10 released.Please note that some users who were using the previous betas may now notice the traffic light icon on more often. It comes on during periods of high loads or when other actions are being taken by the governor. In the previous betas, it did not, so don't be surprised. If it stays on *and* your CPU utilization is not 100%, then something may be amiss in the...
Monday, 7 February 2011
CNET has picked up our last stable/final release of v4.00.33. Release of the new beta is pending, but shouldn't be much longer at all. As an aside, Process Lasso is now ranked #15 in its genre. Keep in mind, it is one huge genre. I'm glad to see it rise above the crapware though, and thank the users for keeping it there.Or get the 64-bit bu...
Sunday, 6 February 2011
I was considering what would make Process Lasso less 'retro' looking without having to do a complete UI overhaul and break accessibility support for the disabled (something many have emailed to appreciate, just FYI to other developers).My brain tells me the installer. That's where I can do it better. I can make it automated. I can make it pretty. I can make it custom. After all, the things an installer does are pretty simple and straight-forward. Create few files, create a few shortcuts.I don't know when this will occur, but you'll see it in the...
Saturday, 5 February 2011
I decided to switch *back* to Windows 7 as my virtual development environment. Why? After extensive testing, I found that it actually performs better on my hardware than does XP. There are a multitude of factors, so we can only surmise why. Mostly, the integration with VMWare Tools is better. The copy&paste quit working in XP. So, anyway, we're back to Windows 7 x32 as my 'virtual build environment' where I keep the last final/stable release. My 'primary build environment' is the physical host, running Windows 7 x64, for those who are...
Friday, 4 February 2011
As I get back to coding, planning both a new final and new beta, I wonder why it is I feel another tooth starting to hurt. WTF is wrong with my body. I have to freaking use big fonts. Man, I am freaking old - 32. Feels more like 45.Anyway, as I said, I do have a new final that is coming too. This is to fix a bug I've been aware of, but hadn't yet fixed until now (the 'processes sometimes show as restrained in GUI even after they have ended restraint'). Turns out the problem was simple, the boolean telling the core engine to send that notification...
Ok, in all the coding and sugar, maybe, just maybe my dental hygiene hasn't been top notch. I'm now being punished with excruciating pain. The good news, it keeps me from getting side tracked on anything else. Anytime I stray from the day's plan, I am put back in place by excruciating pain. I'd go to the dentist, but well, the last dentist I went to made matters worse in many ways, and second, I've always hated dentist. I would rather pull the damn back molar out myself than have another dentist go mucking around carelessly in my mouth. I won't...
Thursday, 3 February 2011
I now get uninstall feedback, as I solicit it (for better or worse). Once read, I can never go back, lol. Fortunately, most of it is actually positive, planning a reinstall, etc.. Anyway, I did have one German user say that he found a superior product. I went and checked it out. It did nothing like Process Lasso, but was a 'PC optimization' type utility I suppose. It hid its 50+MB memory presence with a little trick (paging yourself out). Most authors do it these days, sadly, to hide their true memory footprint. That is why Process Lasso shows...
Wednesday, 2 February 2011
A user reported a crash in the core engine. Giving me accompanying information (and INI, and LOG files), I was able to track down the problem in about 5 minutes. It was a typo, as most bugs are I suppose. Anyway, this was part of the new inter-process communication brought in v4, so only applies to v4+. I have fixed it in a silent update to the last version, a quick new beta refresh is coming shortly, and new official builds coming soon. The new silent update of v4.00.32 is build 89900 with a build date of 2/3/11. It is NOT yet available at the...
Tuesday, 1 February 2011
I released v4.09.16 beta, then discovered I didn't quite finish my testing. I fixed it up, except apparently in XP/2K where the context menu is broken. I'll fix this shortly. These are beta builds, and hence the purpose is to identify any problems. Thanks to those who have reported them. There will be a v4.09.18 beta in a few hou...
Subscribe to:
Posts (Atom)
