Forum Discussion

chicks's avatar
chicks
Regular Contributor
9 years ago

TestExecute crashes with no log produced

Again,  I have submitted a ticket on this but hope somebody else may have encountered this issue or have some advice and suggestions . The problem is that TestExecute starts running my script and t...
chicks's avatar
chicks
Regular Contributor

Hi Robert,   After I changed drivers the problem still occurs.  Does that not mean that it is not the DDT driver?  Although I suppose it could be the same problem with the other excel driver as well.    The problem occurs on both a 32 bit OS and a 64 bit OS.

 

Thanks,  Curt

tristaanogre's avatar
tristaanogre
Esteemed Contributor
9 years ago

It could still be the DDT driver. It sounds like you are "stepping" on a memory location that should not be stepped on... attempting to close a DDT driver that has already been de-allocated for some reason could easily do that.

 

If you can throw together a quick sample of what you are running into, perhaps not your full project, and toss it over this way, I can see if I can help debug.

  • chicks's avatar
    chicks
    Regular Contributor
    9 years ago

    I'd appreciate it but it does not seem to be happening everywhere just on 2 of 3 platforms here and not with all scripts.  Smartbear support has been unable to duplicate the issue. Though I can't tell if they have looked at the windows crash file I've sent them.....

     

    I like the corrupted memory location theory as it seems as if the problem "built up" originally happening only 1 in 10 days and now happening consistently with some scripts.  So more of a "leaky tire" problem, then a "tire fell off" problem. 

     

    I have restarted / rebooted the box but that does not seem to affect the issue.

     

    Let me try to throw together  a general outline of what I'm' doing to see if you have any comments on the driver handling..

     

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      9 years ago

      More than happy to help out. These are the annoying parts of test automation, no matter what the tool... So, always glad to lend a hand.

      • chicks's avatar
        chicks
        Regular Contributor
        9 years ago

        Thanks Alex.  I'll double check the silent log file and report back if it says anything.  As part of smartbear's debug process I tried to capture the report generation file, but when it crashed no file was produced,  so the same thing may be happening with silent log.