Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 595 - AccessViolation when running a C++ Builder XE5 Firemonkey 64-bit application with a TChart and a TPieSeries
Summary: AccessViolation when running a C++ Builder XE5 Firemonkey 64-bit application ...
Status: IN_PROGRESS
Alias: None
Product: FireMonkey TeeChart
Classification: Unclassified
Component: Series (show other bugs)
Version: unspecified
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-21 11:14 EST by yeray alonso
Modified: 2014-03-19 14:14 EDT (History)
1 user (show)

See Also:
Chart Series: Pie
Delphi / C++ Builder RAD IDE Version: RAD XE5


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description yeray alonso 2014-02-21 11:14:03 EST
The same application works fine in 32bit and ocx. And it builds for win 64bits, but I get this when I try to run it:

Project Project1.exe raised exception class $C0000005 with message 'c0000005 ACCESS_VIOLATION'.

And if I click "Continue", then I get this:

Project Project1.exe raised exception class EAccessViolation with message 'Access violation at address 0000000000A36A60 in module 'rtl190.bpl'. Read of address FFFFFFFFFFFFFFFF'.
Comment 1 david berneda 2014-02-24 09:20:11 EST
Problem happens only when compiling "using runtime packages".
The error is raised in FMXTee.Export.Bitmap, initialization.

Its being investigated.
Comment 2 david berneda 2014-02-24 09:29:21 EST
It also happens with any kind of series.

The problem is the internal TeeExportFormats list if a generic TList<TMetaClass> and this is not working fine with C++ when using runtime packages.

One possibility is to replace it with a TList<TClass> or an "Array of TMetaClass", but that (if it works) will mean an important change.
Comment 3 david berneda 2014-03-19 14:14:58 EDT
A fix for this will hopefully come soon, maybe for XE6.