Quote:
Originally Posted by hoopaloopa
FWIW, like said a few times already in this thread, Holdem Indicator was the cause behind Ignition freezing up every 10 minutes.
Been running "smooth" ever since i axed Holdem Indicator.
So the issue w/ all of the processes running is because this is how Ignition/Bodog is now developed. I've tried to explain this in here before. But it's now java, embedded in chrome. So all of your windows and functions it needs to do, it opens a new process (just like chrome). If you open chrome and browse some sites, open task manager and you'll see 15+ processes running (depending on how many windows and plugins you have). Previous to their update, it was just one process (like most desktop apps).
So this is also why it was a highly complex fix. One part of the data for one table would be in process #5, while another part of the data for the same table would be in process #18, and so on. So it was like putting a puzzle back together. On top of that, it's resource intensive, and writing a lot of data to system cache. If you aren't ubber careful on where you're injecting and grabbing this data... crasho.
That's why the first version of card catcher we were seeing crashes as well. We fixed that several weeks back.
Any ways, fyi, for anyone using the catcher there's a major update today and it's posted in the commercial software forum. I'd recommend just shutting everything down before you install and update. One of the reasons some people were still seeing issues is because the DLL for the catcher was still active and locked when they had Ignition open, and they would update the software, but the catcher part wasn't actually updated. This was addressed and fixed as well.
Now lets all cross fingers for no more updates... please! Or at least minor updates that don't change everything completely again.