Pages:
Actions
  • #1 by liltbrockie on 18 Oct 2018
  • Hi there.

    Been getting constant crashed today ...

    Faulting application name: feeder8.exe, version: 8.7.2.3, time stamp: 0x5bc5f5c6
    Faulting module name: KERNELBASE.dll, version: 10.0.17134.319, time stamp: 0x5ea0e53d
    Exception code: 0x0eedfade
    Fault offset: 0x001117d2
    Faulting process ID: 0x3b10
    Faulting application start time: 0x01d466f17631b04f
    Faulting application path: C:\Program Files (x86)\MarketFeeder Pro 8\feeder8.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report ID: 006efb97-b574-476a-aebc-8f90c1250425
    Faulting package full name:
    Faulting package-relative application ID:


    Windows 10 16gb RAM
    The trigger is fairly intensive and looks at horse markets at a 0.5 sec refresh over 10 mins up till in play ... but I wouldn't expect it to crash becasue of it...
    Can anyone help? Can provide the trigger privately if you want.
  • #2 by mcbee on 18 Oct 2018
  • hi
    I need to see the trigger that you are using to see if a loop is been created.

    mcbee
  • #3 by liltbrockie on 18 Oct 2018
  • hmmm not that I am aware of...

    I have turned up the refresh rate for inplay as i dont care about that and it seems to have sorted it out

    If I need to send the trigger I will do ... where can I / how can I send it? It is quite private so certainly dont want to post it to the forum.
  • #4 by liltbrockie on 18 Oct 2018
  • I have noticed also that sometimes markets stop refreshing and there appears the refresh animation under statement and account balance... It stays there constantly 
  • #5 by mcbee on 18 Oct 2018
  • hi
    you need to check your internet connection.
    not sure if you can send the trigger by PM.

    mcbee
  • #6 by liltbrockie on 18 Oct 2018
  • Internet fine I'm on a 100 Meg leased line... Will try and PM
  • #7 by Oxa (WellDoneSoft) on 19 Oct 2018
  • Quote
    The trigger is fairly intensive and looks at horse markets at a 0.5 sec refresh over 10 mins up till in play ... but I wouldn't expect it to crash becasue of it..

    Check if there are any trigger expressions in your triggers (especially with IF function) that use variables which you might forget to initialise. In this case, the expression does not get parsed correctly, it keeps swelling like a snowball and eventually crashes the software.
  • #8 by liltbrockie on 19 Oct 2018
  • There are ZERO IF statements used and ZERO variables used.
  • #9 by mcbee on 19 Oct 2018
  • hi
    up to now I have found a few variables that are not working due to no such variable.
    b_offered_r_ticks(back_price,-1)
    b_offered_r_ticks(back_price,-2)
    b_offered_r_ticks(back_price,-3)
    l_offered_r_ticks(lay_price,1)
    l_offered_r_ticks(lay_price,2)
    l_offered_r_ticks(lay_price,3)

    the correct variables are
    b_offered_back_price-r_ticks(back_price,-1)
    b_offered_back_price-r_ticks(back_price,-2)
    b_offered_back_price-r_ticks(back_price,-3)
    l_offered_lay_price+r_ticks(lay_price,-1)
    l_offered_lay_price+r_ticks(lay_price,-2)
    l_offered_lay_price+r_ticks(lay_price,-3)

    the above are in both lay and back trigger conditions

    I am still testing so maybe find some more.

    mcbee
  • #10 by liltbrockie on 19 Oct 2018
  • Thanks . Appreciate this. 
  • #11 by mcbee on 19 Oct 2018
  • hi
    I am not sure why you have the 2 remember triggers as there conditions are duplicated in the betting triggers and they are every 4 seconds so more strain on the cpu.
    you could use the first condition from the remember triggers and put it in place of the last condition in the betting triggers then move the condition to the first place.
    selections are picked quicker and less triggers.

    mcbee
  • #12 by mcbee on 20 Oct 2018
  • hi
    I have run your original trigger for 3 hours .
    there is no memory leak.
    up to now no crash.
    so still looking.

    mcbee
  • #13 by Oxa (WellDoneSoft) on 22 Oct 2018
  • Hello!

    There was a memory leak after all, which I have now fixed.

    Thank you Mcbee for looking into it, and thank you liltbrockie for reporting it.

    Please re-donwload and reinstall MF Pro.

    I will change the version number later today.
  • #14 by liltbrockie on 22 Oct 2018
  • :-(

    God thats wasted my time... lol

    Anyway ... glad I found it and glad its fixed.... :-)
Pages:
Actions