Reverting a fully tested Win 7 packed OO library from LV-2013 to LV-2011 causes an access violation crash

[Canadian_Horseman]

I've compiled and run a number of packed libraries in LV-2011 SP1 without error.

When I reverted a library created in LV-2013 to 2011 and resolved the linking I get a access violation LV crash on a Windows 7 PC.

I can run the classses targeted, before packing them, without error.

As soon as I pack the library, and call them from the library, I get this access viloation:

0xC0000005 @ EIP=0x055414E0

This is the crash log:

####
#Date: Jul-08-14 1:14:15 PM
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 11.0.1 32-bit
#AppKind: FDS
#AppModDate: 12/12/2011 23:27 GMT
#LabVIEW Base Address: 0x00400000

08/07/2014 2:14:27.914 PM
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 0d089c07-b8c5-416b-8c5f-5c87d9499026
ExceptionCode: 0xC0000005e
¥l»r€¡í

0x01AB8639 - LabVIEW <unknown> + 0
0x01AB8B78 - LabVIEW <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x76E1003F - kernel32 <unknown> + 0
0x77B674DF - ntdll <unknown> + 0
0x77B29EC5 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0

[User002]

The issue was fixed with CAR 356459 and in the LabVIEW 2012 f1 patch. Essentially, LabVIEW will crash if you try to plot exactly 42984 points on an XY Graph. Note: this isn't 100% user controllable as we do a number of things to decimate data for display, but if the user makes sure that LabVIEW will never try to plot more than 40 000 points, the issue shouldn't occur.