# Can't protect memory

**URL:** <https://forum.kx.com/t/cant-protect-memory/8262>\
**Category:** Community Support\
**Tags:** kdb-and-q\
**Created:** [June 16, 2013, 2:00pm UTC](https://forum.kx.com/t/cant-protect-memory/8262 "2013-06-16T14:00:00Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Thompson](https://avatars.discourse-cdn.com/v4/letter/m/8c91f0/32.png) [@Mike\_Thompson](https://forum.kx.com/u/Mike_Thompson)\
**Post date:** [June 16, 2013, 2:00pm UTC](https://forum.kx.com/t/cant-protect-memory/8262/1 "2013-06-16T14:00:00Z")

</div>

If I create a splayed, partitioned table having previously set for compression:  
&nbsp;&nbsp;&nbsp; .z.zd:(17;2;6)

and then subsequent attempt to access this table I get an error message:  
&nbsp;&nbsp;&nbsp;&nbsp; Can’t protect memory

And q.exe quits.

On Windows 7.

KDB+ 3.1 2013.06.14 Copyright (C) 1993-2013 Kx Systems  
w32/ 4()core 4095MB tester testrig 209.33.76.82 PLAY 2013.09.12

q)\l c:\path\to\data  
q)select from t  
Can’t protect memory

I have tried  
&nbsp;&nbsp;&nbsp; .z.zd:(17;1;0)

Same problem.

If I do not compression, then there’s no problem.

A bug?

---

<div class="post-metadata">

**Author:** ![mklee1](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@mklee1](https://forum.kx.com/u/mklee1)\
**Post date:** [June 16, 2013, 2:28pm UTC](https://forum.kx.com/t/cant-protect-memory/8262/2 "2013-06-16T14:28:00Z")

</div>

We hit same problem on solaris Kdb 2.7

We hit once due to a bad query(missed date criteria)? on a compressed hdb

But no such problem when similar bad queries on other tables before

Any clue?

---

<div class="post-metadata">

**Author:** ![charlie1](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@charlie1](https://forum.kx.com/u/charlie1)\
**Post date:** [June 16, 2013, 2:38pm UTC](https://forum.kx.com/t/cant-protect-memory/8262/3 "2013-06-16T14:38:00Z")

</div>

was that solaris

on intel/sparc, 32 or 64bit?

---

<div class="post-metadata">

**Author:** ![mklee1](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@mklee1](https://forum.kx.com/u/mklee1)\
**Post date:** [June 16, 2013, 2:45pm UTC](https://forum.kx.com/t/cant-protect-memory/8262/4 "2013-06-16T14:45:00Z")

</div>

Solaris x86 64bit

---

<div class="post-metadata">

**Author:** ![charlie1](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@charlie1](https://forum.kx.com/u/charlie1)\
**Post date:** [June 16, 2013, 11:22pm UTC](https://forum.kx.com/t/cant-protect-memory/8262/5 "2013-06-16T23:22:00Z")

</div>

I can reproduce the error that Mike observes. We’ll look into it.

thanks

---

<div class="post-metadata">

**Author:** ![charlie1](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@charlie1](https://forum.kx.com/u/charlie1)\
**Post date:** [June 17, 2013, 1:56pm UTC](https://forum.kx.com/t/cant-protect-memory/8262/6 "2013-06-17T13:56:00Z")

</div>

Mike’s problem came in with v3.1T 2013.04.03, affected windows builds only, and is fixed in v3.1 2013.06.17.

Man Kei Lee’s problem is different and I believe relates to insufficient memory resources.

thanks

---

<div class="post-metadata">

**Author:** ![Mike\_Thompson](https://avatars.discourse-cdn.com/v4/letter/m/8c91f0/32.png) [@Mike\_Thompson](https://forum.kx.com/u/Mike_Thompson)\
**Post date:** [September 25, 2013, 8:18pm UTC](https://forum.kx.com/t/cant-protect-memory/8262/7 "2013-09-25T20:18:00Z")

</div>

Hi Charles,

I’m seeing the same issue again.&nbsp;

The combination of Windows and compression is causing q.exe to crash.

Cheers,  
Mike