Menu

#130 Compiled scripts fail to execute

Release 5.6.1r*
closed-fixed
8
2002-11-20
2002-04-13
No

Normally, compiled scripts execute fine. (When I say
compiled I mean saved as runable applications)

After running and quitting Netscape 6, no compiled
script will run immediately after that. The compiled
script will run after the first attempt fails without
any errors.

The effect is the same no matter what compiled script I
run.

Interpreting a script in MacPerl works fine in this
condition, however. The bug only affects compiled scripts.

I have tried launching and running other apps at the
same time (since I assume this is an uninitialized
memory bug) and I always get the same result.

Details:
iMac G4 700 512MB
Mac OS 9.2.2
Netscape Communicator 6.2.1
MacPerl 5.6.1 r1 (2002-3-10)

Discussion

  • Darrell Walisser

    Logged In: YES
    user_id=17701

    I looked into this further and it seems that the apple
    event to run the script is not being generated. I can't find
    where it is generated, but that seems to be the crux of
    the problem.

     
  • Chris Nandor

    Chris Nandor - 2002-05-03
    • priority: 5 --> 8
    • assigned_to: nobody --> neeri
     
  • Matthias Neeracher

    Logged In: YES
    user_id=37219

    Can you reproduce this with Netscape 7? I was unable to.

     
  • Matthias Neeracher

    • status: open --> open-works-for-me
     
  • Chris Nandor

    Chris Nandor - 2002-10-28

    Logged In: YES
    user_id=3660

    I did not try with Netscape 7, and was able to get it with
    Netscape 6, though not entirely reliably.

     
  • Matthias Neeracher

    Logged In: YES
    user_id=37219

    Here's an attempt to deal with this:

    MPAppleEvents.c,1.7
    MPAppleEvents.h,1.2
    MPMain.c,1.8

     
  • Matthias Neeracher

    • assigned_to: neeri --> pudge
     
  • Chris Nandor

    Chris Nandor - 2002-11-20
    • status: open-works-for-me --> closed-fixed
     
  • Chris Nandor

    Chris Nandor - 2002-11-20

    Logged In: YES
    user_id=3660

    This works for me. Please reopen the bug report (or file a
    new one) with more detail if this problem persists.

     

Log in to post a comment.