#6 Crash in 1.9.0 x86 Unicode(b260) on large compares

Enod Barker

Windows 7 SP1 Ultimate 32-bit (fully updated), Regshot 1.9.0 x86 Unicode(b260) using Regshot-x86-Unicode.exe.

Have tested/tried on just a handful of program installations so far. The latest one was a mid-size compare; have done a couple with smaller final text files, one larger (versus this same install using 1.8.3-beta1V5). The regshot.ini files I have set to ignore the same registry keys & directories for both Regshot versions. On the compare, it crashed. Reloaded the saved Shot 1, did another Shot 2, same crash on the compare. Here is the event log info:

Log Name: Application
Source: Application Error
Date: 1/9/2013 8:17:05 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
Faulting application name: Regshot-x86-Unicode.exe, version:, time stamp: 0x50e04358
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b60
Exception code: 0xc0000005
Fault offset: 0x00052cc7
Faulting process id: 0x754
Faulting application start time: 0x01cdee6b8aa40ddc
Faulting application path: C:\Regshot190\Regshot-x86-Unicode.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

This install was not atypical; it was done for Tuesday's Windows Updates. Doing the same compare with 1.8.3-beta1V5 completed without problems (yes, I did shots/compares separately for both Regshot versions).

With 1.8.3-beta1V5, no issues or crashes over a large multitude of two-stage recording and compares of installs since a year ago. With a total of four install recordings, one crash with 1.9.0r260. Good luck getting the bugs out.


News: 2013/01/new-beta-190-r264-released


  • M. Buecher

    M. Buecher - 2013-01-09

    Can you zip up your Regshot.ini and the two shots and attach them to this bug.
    Then we should be able to reproduce and get rid of this bug.

    Thanks for reporting
    Your Regshot Team

  • Enod Barker

    Enod Barker - 2013-01-14

    Thanks for your reply.

    I'm including the regshot.ini file here, but unfortunately, I cannot included shot(s) taken at the time.

    First reason is that I never save second shots for a tracking episode. After the report is made, I just have no need to save second shots (takes up disk space, increases defragging time, etc.). Speaking of which, the 1.9.0 Unicode average single shot size (101 MB) was almost double the size of 1.8.3 ANSI (55 MB) when I was still using 1.9.0.

    Second reason is more important. My first disk shots contain personally identifiable information (name, addresses, bank names, etc. on file names & folders). Thus they cannot be released.

    Hopefully you are still able to find the bug and get 1.9.0 into a usable condition. Thanks again!

    Last edit: Enod Barker 2013-01-14
    • M. Buecher

      M. Buecher - 2013-01-14

      Thanks, I can understand your reasons not to supply regshot hives :)

      The duplicate size is no incident. Regshot saves data as is, and in Unicode builds it gets UTF-16 text data (=2 bytes per char) from Windows. As the majority of registry data is text-based this leads to this increase in size.

      Will try to reproduce by installing a clean Win 7 SP1 Ultimate in a Virtual Machine, take a regshot, then update, then regshot again and compare.

      Your Regshot Team

  • M. Buecher

    M. Buecher - 2013-01-17

    I was able to reproduce, fix added to current development (trunk) in [r261].
    Recognized another issue while testing, when this is fixed a new beta will be released.

    Thanks for reporting
    Your Regshot Team



    Commit: [r261]

  • M. Buecher

    M. Buecher - 2013-01-17
    • status: open --> closed
  • M. Buecher

    M. Buecher - 2013-01-17
    • assigned_to: M. Buecher
  • M. Buecher

    M. Buecher - 2013-01-17
    • labels: --> Crash, Dump, Unicode, Compare

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks