User Avatar Image

Wallace and Gromit demo crashes on startup unless i disconnect from the internet.

posted by DjNDB on - last edited - Viewed by 1.2K users

Here's some awesome bug i can reliably reproduce on my System.

EDIT 1: Just after writing this it now works even with the active internet connection. I'll look into it. Just sad i can't debug it now.

EDIT 2: Some moments later it went back to it's buggy behavior. I made a video this time and will upload and link it here.

EDIT 3 The video demonstration is online now.

The Wallace and Gromit demo crashes on startup unless i disconnect from the internet.
I know it sounds crazy, but I tried it a bunch of times in each situation to make sure the internet connection really is responsible for the bug.
The crash is not just the application process disappearing like in several other cases. It throws an error message. In German it is "WalaceGromitDemo funktioniert nicht mehr". I don't know exactly how the English one is, but it translates to something like "WalaceGromitDemo has stopped working" which I read in a different thread.

At first i just deactivated the network interface in Windows and tested the game several times.
I wasn't sure why it helped, therefore for the next test I disconnected my Internet connection in my router with the same result.

But now it get's really strange. The demo worked before i installed my new graphics card, a Radeon 4850. I have not reinstalled the game since then, therefore data corruption is very unlikely. However i don't know what else has changed softwarewies. It's been a time I played the demo, and since then there were several windows update cycles.
I would try what happens when I reinstall the Nvidia 7600 GT again, but i don't want to change anything big now to keep the bug reproducable.
AS you can see i am more interested in debugging than getting it running, therefore i am not looking for support in this case.

My guess the game tries to connect to telltale, and gets an invalid response of some kind, which causes a buffer overflow which crashes the game.

Maybe something similar is the cause for some of the other startup crashes we see in this forum.

If i am in a good mood i'll check what is transfered before and during the crash with wireshark.

I hope we can figure this out.

For now I'll attach my zipped DxDiag.txt. If you could use any other information for debugging, just ask.
I am confident i can handle it.

27 Comments - Linear Discussion: Classic Style
  • User Avatar Image
    Shauntron Telltale Staff

    That is strange. I'll forward it to the web team. Good detective work :)

  • The problem I have described in http://www.telltalegames.com/forums/showthread.php?t=9354 also seems to be caused by this. Have tried it several times, disconnecting and then reconnecting to the net, and the game (Sam & Max 104) starts fine when I'm not connected.

  • User Avatar Image
    DjNDB Moderator

    @optrirominiluikus said: The problem I have described in http://www.telltalegames.com/forums/showthread.php?t=9354 also seems to be caused by this. Have tried it several times, disconnecting and then reconnecting to the net, and the game (Sam & Max 104) starts fine when I'm not connected.

    That's good news. The more are affected, the more will benefit when it's fixed.

  • User Avatar Image
    DjNDB Moderator

    I made two wireshark captures of the crashing Wallace&Gromit demo.
    I'll attach them here. Maybe they contain anything useful.

  • User Avatar Image
    DjNDB Moderator

    This might be relevant. So far everyone who had exactly this problem is using Vista.

    DjNDB: Windows Vista™ Business
    medintern: Windows Vista Home
    optrirominiluikus: Windows Vista ???

  • User Avatar Image
    DjNDB Moderator

    Qapla'!

    I just woke up and started taking another look at W&G. I was wondering why i didn't ever see any problem reports while it crashed and looked around in windows vista. I found the option to watch problem reports and started digging.

    From there on the major problem was pretty easy to narrow down. Just look at the reports below. There are also two reports that were not related to it. Further ToMI is affected as well.

    I was able to fix it by uninstalling IE8 and therefore running IE7. You can see the exact version information of ieframe.dll in the pictures.

    Since IE8 is delivered automatically via Windows Updates affected people can block it with Microsoft's IE8 Blocker until the problem is resolved.
    It's not really user friendly though and I doubt it is a good solution for inexperienced users, because the update might be necessary at some point and will not be shown again until it is manually unblocked.

    Broken:
    f4373_1248409893.pngWorking:
    1da12_1248409763.pngProblem Reports:

    Produkt
    WallaceGromitDemo.exe

    Problem
    Funktioniert nicht mehr

    Datum
    22.07.2009 17:52

    Status
    Nicht berichtet

    Problemsignatur
    Problemereignisame: APPCRASH
    Anwendungsname: WallaceGromitDemo.exe
    Anwendungsversion: 2009.3.12.21508
    Anwendungszeitstempel: 49b9b5e5
    Fehlermodulname: ieframe.dll
    Fehlermodulversion: 8.0.6001.18783
    Fehlermodulzeitstempel: 4a0515d7
    Ausnahmecode: c0000005
    Ausnahmeoffset: 0012fa32
    Betriebsystemversion: 6.0.6001.2.1.0.256.6
    Gebietsschema-ID: 1031
    Zusatzinformation 1: fd00
    Zusatzinformation 2: ea6f5fe8924aaa756324d57f87834160
    Zusatzinformation 3: fd00
    Zusatzinformation 4: ea6f5fe8924aaa756324d57f87834160



    Produkt
    WallaceGromitDemo.exe

    Problem
    Beendet und geschlossen.

    Datum
    23.07.2009 01:38

    Status
    Nicht berichtet

    Beschreibung
    Aufgrund eines Problems kann dieses Programm nicht mehr mit Windows kommunizieren.

    Problemsignatur
    Problemereignisame: AppHangXProcB1
    Anwendungsname: WallaceGromitDemo.exe
    Anwendungsversion: 2009.3.12.21508
    Anwendungszeitstempel: 49b9b5e5
    Absturzsignatur: 4926
    Absturztyp: 128
    Auf Anwendungsnamen wird gewartet: svchost.exe:DNSResolver
    Auf Anwendungsversion wird gewartet: 0.0.0.0
    Betriebsystemversion: 6.0.6001.2.1.0.256.6
    Gebietsschema-ID: 1031
    Zusätzliche Absturzsignatur 1: c5693575bed56805b370bc072380431d
    Zusätzliche Absturzsignatur 2: 46cd
    Zusätzliche Absturzsignatur 3: a21fa4be2a517bdf4e6ac9fe1228845e
    Zusätzliche Absturzsignatur 4: 4926
    Zusätzliche Absturzsignatur 5: c5693575bed56805b370bc072380431d
    Zusätzliche Absturzsignatur 6: 46cd
    Zusätzliche Absturzsignatur 7: a21fa4be2a517bdf4e6ac9fe1228845e

    Produkt
    WallaceGromitDemo.exe

    Problem
    Funktioniert nicht mehr

    Datum
    23.07.2009 17:05

    Status
    Nicht berichtet

    Problemsignatur
    Problemereignisame: APPCRASH
    Anwendungsname: WallaceGromitDemo.exe
    Anwendungsversion: 2009.3.12.21508
    Anwendungszeitstempel: 49b9b5e5
    Fehlermodulname: StackHash_15ea
    Fehlermodulversion: 0.0.0.0
    Fehlermodulzeitstempel: 00000000
    Ausnahmecode: c0000005
    Ausnahmeoffset: 03d0467e
    Betriebsystemversion: 6.0.6002.2.2.0.256.6
    Gebietsschema-ID: 1031
    Zusatzinformation 1: 15ea
    Zusatzinformation 2: 31558b49dcaef01104f255155eb08c1e
    Zusatzinformation 3: 2a6e
    Zusatzinformation 4: 67d38bb9eabd9b1f79fee3b864bb495b


    Produkt
    MonkeyIsland101.exe

    Problem
    Funktioniert nicht mehr

    Datum
    22.07.2009 19:02

    Status
    Nicht berichtet

    Problemsignatur
    Problemereignisame: APPCRASH
    Anwendungsname: MonkeyIsland101.exe
    Anwendungsversion: 2009.7.6.29796
    Anwendungszeitstempel: 4a52df42
    Fehlermodulname: ieframe.dll
    Fehlermodulversion: 8.0.6001.18783
    Fehlermodulzeitstempel: 4a0515d7
    Ausnahmecode: c0000005
    Ausnahmeoffset: 0012fa32
    Betriebsystemversion: 6.0.6001.2.1.0.256.6
    Gebietsschema-ID: 1031
    Zusatzinformation 1: 9c72
    Zusatzinformation 2: 64a63c849784a033a9bf745993abbdaa
    Zusatzinformation 3: 2ad1
    Zusatzinformation 4: 999b30fe67a078fa00446f6c82bb717d


    Produkt
    MonkeyIsland101.exe

    Problem
    Funktioniert nicht mehr

    Datum
    22.07.2009 19:03

    Status
    Nicht berichtet

    Problemsignatur
    Problemereignisame: APPCRASH
    Anwendungsname: MonkeyIsland101.exe
    Anwendungsversion: 2009.7.6.29796
    Anwendungszeitstempel: 4a52df42
    Fehlermodulname: ieframe.dll
    Fehlermodulversion: 8.0.6001.18783
    Fehlermodulzeitstempel: 4a0515d7
    Ausnahmecode: c0000005
    Ausnahmeoffset: 0012fa32
    Betriebsystemversion: 6.0.6001.2.1.0.256.6
    Gebietsschema-ID: 1031
    Zusatzinformation 1: 9c72
    Zusatzinformation 2: 64a63c849784a033a9bf745993abbdaa
    Zusatzinformation 3: 2ad1
    Zusatzinformation 4: 999b30fe67a078fa00446f6c82bb717d

  • Ah, thanks DjNDB. Think I will just run the game without the internet connection working, as uninstalling IE8 is too much work for me. But hopefully, this will get Telltale on the correct fix.

  • User Avatar Image
    DjNDB Moderator

    @medintern said: Ah, thanks DjNDB. Think I will just run the game without the internet connection working, as uninstalling IE8 is too much work for me. But hopefully, this will get Telltale on the correct fix.

    That's a good solution i guess. Might not work with the treasure hunt though, because it sends data to the website, and i don't think it will do that at a later point without starting the game.

    I am confident that this information will be valuable for telltale and help them to debug the issue.

    I wonder if this also occurs in Windows XP with the same IE8 version.

Add Comment