Tickstory Lite 1.9.8.14 — Export to File Crash on LIGHT.CMD (Object reference not set to an instance of an object)

[Mansa]

Hello Tickstory Team,

I would like to report a reproducible application crash in Tickstory Lite when attempting to export data for LIGHT.CMD.

Environment

• Product: Tickstory Lite
  Version: 1.9.8.14
  Data Provider: Dukascopy
  Instrument: LIGHT.CMD (WTI Light Crude Oil)
  OS: Windows 10/11

Issue Summary

When selecting LIGHT.CMD and choosing Export to File, Tickstory throws an application error and the export process fails.

Other instruments appear to work normally. The issue seems specific to LIGHT.CMD.

Error Message
Object reference not set to an instance of an object.

Full stack trace attached below.

Reproduction Steps

• Open Tickstory Lite 1.9.8.14
  Navigate to:
  Dukascopy -> Commodity
  Select LIGHT.CMD
  Click:
  Export to File
  Application throws exception immediately

Observations

• LIGHT.CMD shows:

Start Date: 2024-01-01
End Date: 2026-02-23

• BRENT.CMD and other commodity symbols appear visible and accessible
  Crash occurs before export configuration completes

Attached Evidence

• Screenshot of instrument selection
  Screenshot of application exception
  Full stack trace/error dump

Question

Could this be related to:

• corrupted metadata for LIGHT.CMD
  invalid historical range handling
  export serializer issue for this symbol
  expired/partial Dukascopy dataset mapping

Please advise whether:

• there is a workaround
  a metadata/database refresh is recommended
  this is a known issue in v1.9.8.14
  a patch or beta build exists that resolves it

Thank you.

Mansa

[tickstory]

Hi Mansa,

Thanks for your comprehensive bug report. We unfortunately can't recreate the issue from the information given, however the error that you provided seems to indicate that it's something to do with the tasks that are currently running rather than the symbol itself.

A couple of questions:

- Could you please tell us if the issue occurs again even if you restart the application?
- Is it occurring immediately after you select "Export to file" or after you press "OK" in the "Export to file" screen.
- Are there any other tasks in the task-list at the time?
- Also, could you please tell us is there is anything specific about your environment? From what you're saying, you tried this under both Windows 10 and 11? Are you working under a specific regional language?

Thanks.

[Mansa]

Thanks for the response.

I’m no longer able to reproduce the issue. After restarting my computer and Tickstory, exports for LIGHT.CMD are now working correctly across all tested timeframes with no crashes.

It may have been a temporary application/task state issue as you suspected.

I’ll reach back out if the issue reoccurs.

Best regards,

[tickstory]

Hi Mansa,

Thanks for letting us know. We've actually done some further analysis on our side and we think we might have found a very specific sequence of actions that might have caused the issue you saw. Although we still can't reproduce it, the fact that a restart fixed it for you seems to confirm this might be the case. We've put in a fix to cover the edge case which will be available in the next update.

Thanks again for the report.