Haxe

the hxcpp & hxcpp-debug-server reinstall somehow fixed it

and that supposedly confirms the problem all along

might have just been that trying to run hxtelemetry stuff just breaks things

what a journey ! well done sticking with it

sometimes messing around with compiler flags and trying to attach stuff like telemetry can maybe break hxcpp

Late to the convo, but: https://github.com/AndreiRudenko/linc_luajit/tree/master/lib/lua/lib/Windows64

I don't think telemetry was the issue though. Might be something to do with the GC settings you changed

Telemetry segfaults happen sometimes but they always show up as telemetry in the stack trace

i mean the main point of worry here is that the issues persisted after the flags for both were removed and the complile caches deleted

and stayed that way till hxcpp was reinstalled

im wondering if well ever actually find out what caused it

anyway now that thats over we can talk about openAL again

Has this been reported before? I was using `flixel.addons.effects.chainable.FlxOutlineEffect` and only got this exception on HashLink. I'm presuming that it is a Lime bug because of this class (`ImageDataUtil`) being from Lime.

It could also possibly be a HashLink bug.

there is no use of static `ImageDataUtil.copyPixels()` inside of here: <https://github.com/HaxeFlixel/flixel-addons/blob/master/flixel/addons/effects/chainable/FlxOutlineEffect.hx>

hang on, let me check what the call stack was

it have to be somewhere behind of here: <https://github.com/HaxeFlixel/flixel-addons/blob/master/flixel/addons/effects/chainable/FlxOutlineEffect.hx#L94>

```haxe
_pixels = FlxDestroyUtil.dispose(_pixels);
_borderPixels = FlxDestroyUtil.dispose(_borderPixels);
```

and then using (target-dependent!) the lime util for

nope, it was from this line in FlxOutlineEffect:

so maybe there is something wrong into using throught Flixel