Since a few days we’ve encountered an error in Sedna. When turning on debug level logging, we get messages like this:
DBG 12/01/2016 15:02:29 (TRN troodonng pid=660 sid=47 trid=-1) [vmmwin32.cpp:_uvmm_map:48]: MapViewOfFileEx failed, address = 0x26DE0000
ERROR 12/01/2016 15:02:29 (TRN troodonng pid=660 sid=47 trid=-1) [vmm.cpp:vmm_preliminary_call:221]: (SE1031) Cannot allocate enough address space segment.
LOG 12/01/2016 15:02:29 (TRN troodonng pid=660 sid=47 trid=-1) [tr.cpp:TRmain:516]: Session is closed
Do you suppose this is a bug in Sedna, or do I need to tweak some settings in Sedna or OS?
I have NOT played around with the ‘-layer-size’ option and the other options for se_cdb. If you think this might be a solution, what options and values do you suggest?
Platform:
I have a feeling this problem is related Windows 10, because we’ve been using Sedna 3.5.161 over a year on Windows 7 without hitting this problem. But this problem happens frequently on the 3 different Windows 10 PCs we are testing on since last week (a laptop, a touchpanel and a VMWare session). (All our PCs have 64 bit OS.)
On Windows 10 I’ve encountered problems with both Sedna 3.5.161 and 3.6.389, and with both 32- and 64-bits binaries.
And I’ve turned off virusscanners, changed compatibility mode to Windows 7 and even Windows Vista. But still the problem remains, although it seems to be less frequently now.
Config:
The database is created with default settings, apart from ‘-db-security “authorization”’.
I’ve tried both default ‘session stack depth’ and with a value of 30000 => Seems to make no difference.
Log files:
See line 656 in the attached log file.
I’ve also put some more logfiles (with debug level logging) online: http://share.aweta.nl/weblinks/?id=7895fc13088ee37f511913bac71fa66f&filename=SednaError
Clients:
Python programs using the zif.sedna driver.
Best regards,
Marco van der Putten (mvdputten@aweta.nl)
Anonymous
We haven't check it it yet (it takes some time to get developer station set up with windows 10) but it could be not related to Sedna itself.
The interesting point in logs is "MapViewOfFileEx failed, address =
". That can be a sign that RAM of the computer is corrupted. Could you run memtest for a night to see that everything alright with it? ( http://www.memtest.org/ http://www.memtest.org/ -- there are prebuilt ISO files that you can boot into.)Nethertheless we'll try to reproduce the bug as soon as Win10 machine will be ready to use
Oleg Borisenko, Sedna team
Related
Bugs: #102
Oh, I missed the line where you telling that it reproduces on 3 different PC. We'll take a look soon
Oleg Borisenko, Sedna team
Related
Bugs: #102