Skip to main content
Known Participant
March 22, 2012
Question

ADL in Adobe AIR 3.1 crashes then works then crashes then works

Hi,

I'm using Adobe AIR 3.1 to create an HTML/Javascript application.

Whenever I go to run the application using "adl", I'll get the message "Adobe AIR Debug Launcher has stopped working".  If I repeat this several times, the application will eventually come up and run normally. The next time I try to run it, it may crash again, even if I've made no changes.

I'm on Windows 7 x64. In the event viewer, the errors seem to occur in either RASAPI32.dll or rtutils.dll.

Faulting application name: adl.exe, version: 3.1.0.4880, time stamp: 0x4eb7612e

Faulting module name: RASAPI32.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdad7

Exception code: 0xc0000005

Fault offset: 0x000017e9

Faulting process id: 0x1f54

Faulting application start time: 0x01cd07c139760fb3

Faulting application path: C:\PF86\Adobe\AirSDK\bin\adl.exe

Faulting module path: C:\Windows\system32\RASAPI32.dll

Report Id: 7b7c9ecc-73b4-11e1-ace3-bcaec51b8285

Faulting application name: adl.exe, version: 3.1.0.4880, time stamp: 0x4eb7612e

Faulting module name: rtutils.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b9ac

Exception code: 0xc0000005

Fault offset: 0x000012c8

Faulting process id: 0x1df0

Faulting application start time: 0x01cd07bd9cfe7082

Faulting application path: C:\PF86\Adobe\AirSDK\bin\adl.exe

Faulting module path: C:\Windows\system32\rtutils.dll

Report Id: de3b1cf6-73b0-11e1-ace3-bcaec51b8285

I downloaded the AIR 3.1 SDK, copied over a few Javascript files and only use "adl" for running the program. I haven't tried to build an application yet.

This topic is closed to new replies. Start a new post to keep the conversation going.

8 replies

Known Participant
April 3, 2012

I thought I would post my little test application. Maybe someone else has run into this same problem and knows a work-around. The application works fine when packaged up, it only fails (sometimes) when using adl.

All the code does is to try to read a URL using URLStream. I've tried using URLLoader instead. Same problem. I've tried delaying the read with a five second timeout. I tried adding a button and initiating the read only after the button was clicked. I tried adding all the event handlers for the URLStream.load() method.  None of this helped. The programs sometimes finished OK and sometimes didn't. Once it starts up OK, I have no further problems (in my real application). There's clearly a race condition in the the first attempt to load a URL when using "adl".

Since there aren't a lot of people yelling about this, I am either doing something unusual or my environment is unusual (Windows 7 x64) or both.

Crash.js

var ready = function()

{

    // Display the window

    nativeWindow.activate();

    // Causes crash

    crash();

};

var crash = function()

{

    try {

    var url = new air.URLRequest('http://www.google.com/');

    var stream = new air.URLStream();

    stream.load(url);

    alert("Done");

    }

    catch (error) {

    alert(error);

    }

};

Translate
chris.campbell
Legend
March 22, 2012

Hi Tony,

I'm sorry you're running into this crash.  Would you mind generating a crash dump so we can take a look at the call stack?  See this post for details.  Once generated, please open a new bug report at bugbase.adobe.com and provide both the crashlog and sample code/application if you can.  Please post back with the bug URL or number once done.

Out of curiosity, does this occur if you try running your app on a new user account?

Thanks,

Chris

Translate
Known Participant
March 24, 2012

Hi, Chris,

Thanks for helping. The bug is 3148469.

I tried running the program in a freshly created account. The first 3 times it worked. The fourth it crashed.

Translate