# EXCEPTION\_ACCESS\_VIOLATION on Windows but not MacOS

**URL:** https://discourse.julialang.org/t/exception-access-violation-on-windows-but-not-macos/127653
**Category:** General Usage
**Created:** [April 3, 2025, 1:38am UTC](https://discourse.julialang.org/t/exception-access-violation-on-windows-but-not-macos/127653 "2025-04-03T01:38:29Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![danielwe](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/danielwe/32/35657_2.png) [@danielwe](https://discourse.julialang.org/u/danielwe)
#### Post date: [April 25, 2025, 4:25pm UTC](https://discourse.julialang.org/t/exception-access-violation-on-windows-but-not-macos/127653/17 "2025-04-25T16:25:52Z")

</div>

> [@lewis](#):
>
> The array indices in comprehension is more costly

Oh, interesting, this is a regression in Julia 1.11. In Julia 1.10, the `eachindex` and `zip` versions perform identically. What’s happening is probably the same as in this thread: [Nextfloat is slower on 2D array than on 1D array - #8 by Oscar\_Smith](https://discourse.julialang.org/t/nextfloat-is-slower-on-2d-array-than-on-1d-array/128380/8); that is, inboundsness is no longer inferred when using `eachindex` on 2D (or higher-dimensional) arrays.

---

_[View the full topic](https://discourse.julialang.org/t/exception-access-violation-on-windows-but-not-macos/127653)._