cancel
Showing results for 
Search instead for 
Did you mean: 

Can't protect memory

Mike_Thompson
New Contributor

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

and then subsequent attempt to access this table I get an error message:
     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
    .z.zd:(17;1;0)

Same problem.

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

A bug?


6 REPLIES 6

mklee
New Contributor

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?

charlie
New Contributor II
New Contributor II
was that solaris
on intel/sparc, 32 or 64bit?

mklee
New Contributor

Solaris x86 64bit

charlie
New Contributor II
New Contributor II
I can reproduce the error that Mike observes. We'll look into it.

thanks

charlie
New Contributor II
New Contributor II
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

Hi Charles,

I'm seeing the same issue again. 

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

Cheers,
Mike