Marketfeeder Pro has stopped working - Problem log attached

Hi Guys,

I have an issue in that a can load a trigger and the trigger will run successfully but when I click on "Program Logs" I get an error message saying "Marketfeeder Pro has stopped working." When I click the "Problem Email" I get the output listed below.

The issue appears to be trigger related, when I load a basic out of the box trigger things work as expected and the program log button works fine. I have reinstalled MFP on different machines and the same behaviour is observed each time.

Is anyone from MFP able to look at the Problem details and give me some advice on next steps.




Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   feeder8.exe
  Application Version:   8.0.0.15
  Application Timestamp:   00000000
  Fault Module Name:   feeder8.exe
  Fault Module Version:   8.0.0.15
  Fault Module Timestamp:   00000000
  Exception Code:   c0000005
  Exception Offset:   001da807
  OS Version:   6.1.7601.2.1.0.272.7
  Locale ID:   1033
  Additional Information 1:   5fda
  Additional Information 2:   5fda7dd031617c191e916073bfa7e257
  Additional Information 3:   5eea
  Additional Information 4:   5eea22c2ee2632885d3a4eed35554e99

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Hi Guys,

Is someone able to look at this for me please.

Steve

Hello,

What are the names of your triggers inside the file you are running?

Hi Oxa,

The trigger names are as follows;


maximum_bank - just store the highest value of the bank since the last MFP restart -  (not used in any calculations)

current_recovery_step - update if currentloss gt 0 and currentstep eq 999 (loss was not fully recovered)

current_loss -Increase current_loss when we back a selectionl that wins the race

current_loss - Reduce currentloss

Reset current_loss to 0 once all losses have been recovered

Reset current_loss to 0 once current_loss exceeds maximum_loss

Place bet - We are currently recovering a loss

Place bet - We are currently recovering a loss - update current_recovery_step (This just updates current_recovery_step and does NOT place a bet)

Place bet - we arent recovering any losses  and we have unsettled races

Place bet - Extra bet (Only place this bet if the current loss eq 0)

Try renaming triggers so that they don't have parentheses and hyphens in their names.

Hi Oxa,

I have removed all hyphens, underscores and brackets and the same thing is still happening.

Do you have any more ideas?

Steve

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   feeder8.exe
  Application Version:   8.0.0.15
  Application Timestamp:   00000000
  Fault Module Name:   feeder8.exe
  Fault Module Version:   8.0.0.15
  Fault Module Timestamp:   00000000
  Exception Code:   c0000005
  Exception Offset:   00410b86
  OS Version:   6.1.7601.2.1.0.272.7
  Locale ID:   1033
  Additional Information 1:   48f5
  Additional Information 2:   48f5ca2b9a3905de8f44f8f4b846ebf4
  Additional Information 3:   4b58
  Additional Information 4:   4b58193079402583a598bdd8868c80e1

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Hi Guys some more information on this is as follows;

If I click on the "Program logs" link in MFP it opens up chrome with the following URL "http://127.0.0.1:19001/#program".

If I restart MFP and log in and let everything start up as normal everything is fine until I click the "Reload this page" icon in Chrome and then MFP just crashes again.

I have also tested with IE, and tested on multiple computers. One is my notebook and the other is a VPS.

I would really appreciate some help because I cannot debug anything in the current state.

Regards
Steve

I forgot to mention that you need to remove the old logs (the ones that were generated for triggers with parentheses in them) - they could be still crashing the program.

The folder to remove is:

c:\Users\%username%\MarketFeeder Pro 8\profiles\%profile name%\logs\triggers\

Hi Oxa,

Its still giving problems, if I upload it can you have a quick look at it to see what is crashing MFP please?

Steve

Thanks Oxa, its like there is still something dodgy in the trigger file somewhere.

I am rebuilding it from scratch which to be honest is something I was looking to do at some stage anyway. If I have problems later I'll give you call.

Thanks
Steve

Hi Oxa,

This has started happening again and I am starting to get paranoid that this is only happening to me.

Can you please let me know what characters are allowed and which ones arent and if there is any limits on the number of characters etc. for the triggers.

Thanks
Steve

Hi Oxa,

This has started happening again and I am starting to get paranoid that this is only happening to me.

Can you please let me know what characters are allowed and which ones arent and if there is any limits on the number of characters etc. for the triggers.

Thanks
Steve

Hi Steve

I in past have many problems like you have and somehow they trully are linked to the names of trigger, blocks and also trigger file.

For exemple now i use thios rules and all is ok:

Names that contains mfp keywords like back i use Back or bk
i dont use any symbol like , . : ; _ % & etc
i dont use letters like ç, ã etc

so there it goes an exemple

If i wont name a trigger like this:

"back favourite and at best price"
i use
"Bk Fav Bst Prce"

Hope that helps you.

Chears
pcal72

Thanks for your reply pcal72. I appreciate the response.

In my attempt to name the triggers properly this is exactly what I am doing wrong.

Thanks again.

Hi pcal,

I dont suppose you have a list of the MFP keywords do you?

Also, are they case sensitive?

Steve

Hi pcal,

I dont suppose you have a list of the MFP keywords do you?

Also, are they case sensitive?

Steve

Hi Steve

To avoid that problems i always use all words like this.

Orinal name : back favourite lay price

Rename to : Back Fav Lay Price
OR
most commun : BackFavLayPrice

So i always use capital letters whith other ones
pcal72