Bloody bugs again!
I have been working on those pesky bugs again, and have just had the classic 2 continues and freeze, but this time having attached the debugger from Microsoft Visual Studio.
The events are as follows:-
1) Launch casino and then launch Loaded tournament.
2) Buy continue and play.
At this point, nothing untoward seems to be happening, both casinogame processes are using a modest 0 to 3% of the processor.
Now comes the story of how the bug grows.
3) Buy following continue and play.
Now, whilst everything still APPEARS to be OK, the tournament casinogame module is now burning through 25% of the processor capacity whilst not obviously doing anything more demanding than the previous continue where it was around 2%.
4) Buy following continue.
At this point, after a short delay the sound stops and everything freezes. The continue IS in fact bought successfully, but instead of going back to the game, the window has frozen in "buy continue" mode as though the continue hasn't been bought.
Despite being completely unresponsive, the module is STILL burning through 25% of the processor capacity.
Even if the casino than gets picked up by Windows as a non responding app and closed via the Windows reporting system (app not responding, windows is looking for a solution, close, etc), the faulting casinogame module is STILL there, burning through the same 25% of processor capacity, but with a drastically reduced allocation of memory. Only the task manager can get rid of it.
During all of this, Visual Studio catches the following:-
The thread 0x143c has exited with code 0 (0x0).
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
The thread 0x10d4 has exited with code 0 (0x0).
The thread 0x113c has exited with code 0 (0x0).
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
The thread 0x1998 has exited with code 0 (0x0).
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
The thread 0x1bb8 has exited with code 0 (0x0).
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
Exception thrown at 0x7674C42D in casinogame.exe: Microsoft C++ exception: Js::JavascriptExceptionObject at memory location 0x0018E314.
The thread 0x1064 has exited with code 0 (0x0).
the javascript errors seem to be considered no big a deal, just an irritating condition that should not cause any problems.
What IS more important is this:-
Exception thrown at 0x767C30E8 (kernel32.dll) in casinogame.exe: 0xC0000005: Access violation reading location 0x00000000.
This seems to be a "null pointer" issue trying to access memory location zero, which of course doesn't exist.
It would now seem that this might be an issue with Windows 64 bit systems, and there is even an official Microsoft article about the problem:-
Old / Expired Link
It looks pretty complicated too.
As far as Microgaming is concerned, this for me seems to be confined to the 32Red client when playing the 20K tournament, and others have also been reporting this. Maybe the common factor is a 64bit Windows OS. I had the same problems on my Windows 7 laptop, also a 64bit OS.
The 32Red client is doing something during tournament play that the Dash client is not, as the Dash client does not exhibit this bug.
It's a problem for players as this article is clearly for "advanced users", and your average user would probably not even find it, let alone be confident in applying the hotfix detailed within (no evidence as yet that it would work in this case anyway).
It would therefore be preferable for Microgaming to figure out why some of their clients suffer this, whereas others don't.
At least one player here has reported this same problem with the tournament, but not in the 32Red client. I only have 2 of the 4, soon to be 3 of the 5 once Roxy Palace is properly absorbed.
" This is something used for displaying websites in a browser. I might expect to see these in the lobby process, but certainly not in the process that is running the tournament itself. Of course, it does raise the possibility that something is interfering with the tournament process and destabilising it. This could be a third party program or service that is used by some, but not all, players. This might mean that some players don't see this problem at all, and others see it slightly differently. I have seen 32Red have all the problems, but Dash has been relatively trouble free, other than the Santa's Wild Ride memory leak syrup issue that occurs in both 32Red and Dash, and on every PC and Laptop I have tried it on.
but I mean there are 6 or 7 players who look like they could be "going for it" so to speak with the full £2500 
. Man i played that stupidly.. But i learn from my mistakes, i will just propably aim to 5-8th if things are not going my way, an if they are then i will aim for the top spot.
