BSoD Packager for AIR

[Guest]

I'm running v1 of TCS on a Dell Optiplex 755 w/4GB RAM. When I run RoboHelp Packager for AIR on any output, repeat "any output," after I review the output and exit the packager, I get a BSoD. This is dependable and replicable...10 times so far today trying to diagnose it. Test has rulled out a RAM issue. Any advise?

[Captiv8r]

Hi there

When you see the BSoD, does it cite a particular DLL? I ask because I used to get BSoD regularly and thought it was related to one thing when it was another.

You also cite 4 Gigs of RAM? Does this mean you are running a 64 bit OS? If so, perhaps that has something to do with things. I don't believe TCS has been certified to run on a 64 bit OS.

Cheers... Rick

[Guest]

I've had several spontaneous crashes on mdbms.dll, but the BS doesn't mentioned a pain point.

I'm running 4GB on 32bit XP Pro SP2.

[Guest · Accepted solution]

I may have found the issue:

When I spin an AIR application from WebHelp output and preview the AIR application, or
when I Preview an application from the AIR Packager Generate dialog,
if I Cancel the dialog before I close the AIR application, the OS will BSoD every time;
if I Cancel the Generate dialog without first closing the AIR application, the AIR Packager exits and returns control to me without error, every time.

This sounds like a memory management bug of a garbage collection bug.

When I close the fresh AIR application before I exit the AIR Packager, apparently the AIR Packager attempts to clear memory, finds that <some address> is already clear, and barfs with "PAGE_FAULT_IN_NONPAGED_AREA" every time.

[Peter Grainge]

I can only add that this issue has not been reported by anyone else on this forum or on HATT.

[Guest]

Beg to differ, the issue has certainly been reported, but the resolution has not.

I took an unconventional approach to a BSoD event. After I eliminated the obvious causes, I stumbled upon something that works...closing the packager before closing the AIR application, and works every time, so far.

[Guest]

Beg to differ, the issue has certainly been reported, but the resolution has not.

After I eliminated the obvious causes, I took an unconventional approach to the BSoD event and stumbled upon something that works...closing the packager before closing the AIR application, and works every time, so far.

[Peter Grainge]

Can you point me to the posts please?