Post Processor Crash Issue

[terrence.matthews]

Creating post for user

Crash Issue: "This occurred when I was trying to run the post processor - an operation that normally runs with no issue. (I made a small mod to one part and regenerated the paths and ran the post processor) I filed a crash report - the number is 314036117"

[DeeEmm]

The File...

[DeeEmm]

Still crashing - report #320727030

Crashed when I tried to change focus to app - similar to previous crashes.

I don't use this app very often, but when I do it will invariably crash.

I cannot believe that it is getting on for a year since I originally reported this issue and it is still no closer to being resolved.

I really feel that support are giving me the runaround. I've lost count of the number of support techs that have looked at this, each time it just got hand balled. Then it was hand balled to these forums. Now we are at the stage where my last post did not even get a reply.

 I've reopened  the original ticket and asked for this to be escalated.

I will ask here too for this issue to be escalated.

Thanks

[DeeEmm]

Out of the many hundreds of crashes I have experienced each time is different so your post title is misleading.

[DeeEmm]

so it looks like I cannot reopen the ticket and I cannot create a new ticket. Whilst support was current at the time I originally raised this issue, because it is no longer current I am unable to create a new ticket.

I suggest that as the original issue was never resolved the ticket be reopened and esalated.

thanks

[karina.harper]

Hi @DeeEmm 

Looking at your crash reports again, it seems that you have crashed once since January. The crash is a UI related issue that the team is tracking. As you said, related to focus and not unique to your system.

I can add a note that you have reported this to the internal ticket. A crash every now and then is not unexpected behavior, that's why we have the recovery document feature.

Cheers,

Karina

[DeeEmm]

Respectfully, a crash every now and then would be acceptable. But it happens EVERY TIME I USE THE APP. 

The frequency between reports is no indication of the frequency of use.  There have actually been several crashes since January each of which I have reported. Each crash report I have linked back to the original ticket #. You assured me they were being collected 'in a bucket', so where are those additional crash reports if you cannot see them? Was this 'bucket' cancelled when the ticket was closed? I was assured that the ticket would remain open until the issue was resolved but it was closed despite my complaints that the issue was not fixed.

Essentially each time I use the app it crashes.  That is a 100% failure rate. I am sure that you can verify this with usage stats. 

To note: I have just made yet another report. 

I have tried to get the orignal ticket reopened as this forum has been unable to remedy the issue, but this has not been possible. 

Where do we go from here????

I was assured that this was the correct pathway to fixing this issue by Terence who appeared to just want to hand ball the issue. However now I just get told that this is expected behaviour. For a product that costs $60+ a month I honestly expect more and I am sure that the CBS and OCBA would agree.

How do I escalate this issue to get it resolved properly?

Regards

Mick.