"OpenGL4MatlabDemos" errors

Has anyone any ideas why I'm gettig always errors like this with the
OpenGL4MatlabDemos:

----------------------------------------------------------------------
--
Segmentation violation detected at Wed May 30 13:41:48 2007
----------------------------------------------------------------------
--

Configuration:
MATLAB Version: 7.3.0.267 (R2006b)
MATLAB License: 29577
Operating System: Microsoft Windows XP
Window System: Version 5.1 (Build 2600: ServicePack 2)
Processor ID: x86 Family 6 Model 13 Stepping 8, GenuineIntel
Virtual Machine: Java 1.5.0 with Sun Microsystems Inc. Java HotSpot
(TM) Client VM mixed mode
Default Charset: windows-1250

Register State:
EAX = 00000000 EBX = 25aec2b4
ECX = 25ab7c00 EDX = 25ab7c00
ESI = 00000000 EDI = 25ab7c00
EBP = 25ab7c00 ESP = 00d1cd00
EIP = 690d7148 FLG = 00010246

Stack Trace:
[0] atioglxx.dll:0x690d7148(0x6932f8a0, 0x6932f8b0, 0x6932ff50,
0x6932ff50)
[1] atioglxx.dll:0x6932f890(0xc308c483, 0xcccccccc, 0xa9e85152,
0x83000e8d)
[2] 0x000e8db8

This error was detected while a MEX-file was running. If the MEX-file
is not an official MathWorks function, please examine its source code
for errors. Please consult the External Interfaces Guide for
information
on debugging MEX-files.

If it is an official MathWorks function, please
follow these steps in reporting this problem to The MathWorks so
that we have the best chance of correcting it:

1. Send this crash report to segv@... for automated
analysis.
For your convenience, this information has been recorded in:
C:\DOCUME~1\c\LOCALS~1\Temp\matlab_crash_dump.1272

2. If the problem is reproducible, please submit a bug report via:

http://www.mathworks.com/support/contact_us/ts/help_request_1.html

Thank you for your assistance. Please save your workspace and restart
MATLAB before continuing your work.

Error in ==> SpinningMovieCube at 57
[win , winRect] = Screen('OpenWindow', screenid);



My config is:
Acer Travelmate 8104
Intel Pentium M760 processor
Ati Mobility Radeon X700 with 128MB
1GB DDR2 RAM
OS: WinXP with SP2
Does it only happen with OpenGL demos or also with other
demos? The most recent PTB beta in use? A first good step
is always a driver update. ATI drivers on Windows are often
broken in very impressive ways, especially the ones for mobile
chips, don't know why.

Try if you get any interesting debug output if you call

Screen('Preference', 'Verbosity', 6);

before running one of the crashing demos.

If its only OpenGL demos then its a good check to download
and run some OpenGL demos from the Internet and see if they
work well or if they die as well.

-mario

--- In psychtoolbox@yahoogroups.com, "csabacziraki" <csabacziraki@...> wrote:
>
> Has anyone any ideas why I'm gettig always errors like this with the
> OpenGL4MatlabDemos:
>
> ----------------------------------------------------------------------
> --
> Segmentation violation detected at Wed May 30 13:41:48 2007
> ----------------------------------------------------------------------
> --
>
> Configuration:
> MATLAB Version: 7.3.0.267 (R2006b)
> MATLAB License: 29577
> Operating System: Microsoft Windows XP
> Window System: Version 5.1 (Build 2600: ServicePack 2)
> Processor ID: x86 Family 6 Model 13 Stepping 8, GenuineIntel
> Virtual Machine: Java 1.5.0 with Sun Microsystems Inc. Java HotSpot
> (TM) Client VM mixed mode
> Default Charset: windows-1250
>
> Register State:
> EAX = 00000000 EBX = 25aec2b4
> ECX = 25ab7c00 EDX = 25ab7c00
> ESI = 00000000 EDI = 25ab7c00
> EBP = 25ab7c00 ESP = 00d1cd00
> EIP = 690d7148 FLG = 00010246
>
> Stack Trace:
> [0] atioglxx.dll:0x690d7148(0x6932f8a0, 0x6932f8b0, 0x6932ff50,
> 0x6932ff50)
> [1] atioglxx.dll:0x6932f890(0xc308c483, 0xcccccccc, 0xa9e85152,
> 0x83000e8d)
> [2] 0x000e8db8
>
> This error was detected while a MEX-file was running. If the MEX-file
> is not an official MathWorks function, please examine its source code
> for errors. Please consult the External Interfaces Guide for
> information
> on debugging MEX-files.
>
> If it is an official MathWorks function, please
> follow these steps in reporting this problem to The MathWorks so
> that we have the best chance of correcting it:
>
> 1. Send this crash report to segv@... for automated
> analysis.
> For your convenience, this information has been recorded in:
> C:\DOCUME~1\c\LOCALS~1\Temp\matlab_crash_dump.1272
>
> 2. If the problem is reproducible, please submit a bug report via:
>
> http://www.mathworks.com/support/contact_us/ts/help_request_1.html
>
> Thank you for your assistance. Please save your workspace and restart
> MATLAB before continuing your work.
>
> Error in ==> SpinningMovieCube at 57
> [win , winRect] = Screen('OpenWindow', screenid);
>
>
>
> My config is:
> Acer Travelmate 8104
> Intel Pentium M760 processor
> Ati Mobility Radeon X700 with 128MB
> 1GB DDR2 RAM
> OS: WinXP with SP2
>
I have this error only with the "OpenGL4MatlabDemos".
Yes, I use the most recent PTB beta:

>> PsychtoolboxVersion
ans =
3.0.8 - Flavor: beta - Corresponds to SVN Revision 774

I have the newest (Acer TravelMate) ATI driver:
(8.163WHQL-050809a1-026573C-Acer)

When I run this: Screen('Preference', 'Verbosity', 6);
I get only a new varible (ans) in the workspace with value "3" and
after this when I run any of the "OpenGL4MatlabDemos" I have the same
error message what I posted.

Not Matlab applications with OpenGL work fine and not Psychtoolbox
OpenGL demos also.

Any suggestion?


--- In psychtoolbox@yahoogroups.com, "Mario Kleiner"
<mario.kleiner@...> wrote:
>
> Does it only happen with OpenGL demos or also with other
> demos? The most recent PTB beta in use? A first good step
> is always a driver update. ATI drivers on Windows are often
> broken in very impressive ways, especially the ones for mobile
> chips, don't know why.
>
> Try if you get any interesting debug output if you call
>
> Screen('Preference', 'Verbosity', 6);
>
> before running one of the crashing demos.
>
> If its only OpenGL demos then its a good check to download
> and run some OpenGL demos from the Internet and see if they
> work well or if they die as well.
>
> -mario
Great! Your newest drivers are only 1.7 years old. Great customer
support Acer, love it.

Go here...

<http://ati.amd.com/support/drivers/xp/mobility-xp.html>

...download their checking tool: It will tell you if you can use
ATI's monthly updated mobile gfx-drivers on your machine,
instead of that hopelessly outdated c%$~!p from Acer.

The same webpage also lists names of notebook vendors
that seem to care a bit more about their customers, i.e., they
design their systems in a way that allows customers to enjoy
monthly driver updates from ATI instead of having to rely on
a support site that doesn't care about support.

PTB pushes the graphics hardware pretty hard, doing unusual
things in some places, so its more likely to spot bugs in the
drivers. I'd guess its our OpenGL context isolation causing the
crash due to some driver bug. The only other trouble makers
would be creation of a z- and stencilbuffer, but many other
OpenGL apps/demos at least need a z-buffer so thats less
likely. You can downgrade your beta to revision 601, by
running UpdatePsychtoolbox(PsychtoolboxRoot, '601');

This will remove context isolation, so if that was the reason,
then the demos should work after the downgrade. Of course
you will also lose all improvements and bug fixes of the last
5 months and filing any future problem reports for that version
is pointless.

Do you need 3D graphics support?

-mario

--- In psychtoolbox@yahoogroups.com, "csabacziraki" <csabacziraki@...> wrote:
>
> I have this error only with the "OpenGL4MatlabDemos".
> Yes, I use the most recent PTB beta:
>
> >> PsychtoolboxVersion
> ans =
> 3.0.8 - Flavor: beta - Corresponds to SVN Revision 774
>
> I have the newest (Acer TravelMate) ATI driver:
> (8.163WHQL-050809a1-026573C-Acer)
>
> When I run this: Screen('Preference', 'Verbosity', 6);
> I get only a new varible (ans) in the workspace with value "3" and
> after this when I run any of the "OpenGL4MatlabDemos" I have the same
> error message what I posted.
>
> Not Matlab applications with OpenGL work fine and not Psychtoolbox
> OpenGL demos also.
>
> Any suggestion?
>
>
> --- In psychtoolbox@yahoogroups.com, "Mario Kleiner"
> <mario.kleiner@> wrote:
> >
> > Does it only happen with OpenGL demos or also with other
> > demos? The most recent PTB beta in use? A first good step
> > is always a driver update. ATI drivers on Windows are often
> > broken in very impressive ways, especially the ones for mobile
> > chips, don't know why.
> >
> > Try if you get any interesting debug output if you call
> >
> > Screen('Preference', 'Verbosity', 6);
> >
> > before running one of the crashing demos.
> >
> > If its only OpenGL demos then its a good check to download
> > and run some OpenGL demos from the Internet and see if they
> > work well or if they die as well.
> >
> > -mario
>
Jap. The problem is that ACER doesn't design their notebooks
in a compliant fashion so they need these customized drivers
and that they don't care too much about customer support,
otherwise they would at least provide half-yearly
updates of their drivers.

So the best solution for ACERs bug would be to ask them to
provide a driver update. Your gfx-card will also be incapable
of supporting any of the new features of PTB although the
hardware can do it, just insufficient outdated drivers.

And its probably a good idea for Windows users to check the
webpages of graphcis vendors like ATI or NVidia before they
buy a portable and prefer a vendor that allows use of the
generic drivers - that way at least you get timely driver
updates.

The next beta release will contain a switch to disable context
isolation for such broken systems. Then PTB will work with
OpenGL, but without the additional protection layer: Much
more time spent for you to hunt down bugs in your own
OpenGL code or finding unwanted interactions with PTB, not
fun at all. I already spent a workday on hunting such ghosts
in my own experiment code -- and i'm at a big advantage
knowing how everything works, so good luck for you if you
hit such a problem.

-mario


--- In psychtoolbox@yahoogroups.com, "csabacziraki" <csabacziraki@...> wrote:
>
> The problem is that the Acer TravelMate Notebooks
> with ATI videocards need ACER customized display drivers.
> The available newest version from this customized display driver is
> what I have now (8.163WHQL-050809a1-026573C-Acer).
> Sadly I don't know how they (ACER) have been modified the original
> Catalyst Mobility Display Driver (I guess this information is not
> public)
> so I can't use the newer original Catalyst Mobility Display Driver
> versions.
>
> The display driver checking tool
> (http://ati.amd.com/support/drivers/xp/mobility-xp.html) says also:
>
> "Thank you for your interest in CATALYST™.
> Unfortunately, this software update cannot be installed on your
> system.
> Please contact your notebook manufacturer for driver updates."
>
> After I have downgraded my psychtoolbox beta to revision 601 (running
> UpdatePsychtoolbox(PsychtoolboxRoot, '601');) every OpenGL4MatlabDemo
> works fine.
> Accordingly I think probably really the "OpenGL context isolation"
> causing this crash.
> Have you got any idea how to work around this bug without downgrading
> the Psychtoolbox?
> What do you suggest what would be the best solution for this bug?
>
>
> --- In psychtoolbox@yahoogroups.com, "Mario Kleiner"
> <mario.kleiner@> wrote:
> >
> > Great! Your newest drivers are only 1.7 years old. Great customer
> > support Acer, love it.
> >
> > Go here...
> >
> > <http://ati.amd.com/support/drivers/xp/mobility-xp.html>
> >
> > ...download their checking tool: It will tell you if you can use
> > ATI's monthly updated mobile gfx-drivers on your machine,
> > instead of that hopelessly outdated c%$~!p from Acer.
> >
> > The same webpage also lists names of notebook vendors
> > that seem to care a bit more about their customers, i.e., they
> > design their systems in a way that allows customers to enjoy
> > monthly driver updates from ATI instead of having to rely on
> > a support site that doesn't care about support.
> >
> > PTB pushes the graphics hardware pretty hard, doing unusual
> > things in some places, so its more likely to spot bugs in the
> > drivers. I'd guess its our OpenGL context isolation causing the
> > crash due to some driver bug. The only other trouble makers
> > would be creation of a z- and stencilbuffer, but many other
> > OpenGL apps/demos at least need a z-buffer so thats less
> > likely. You can downgrade your beta to revision 601, by
> > running UpdatePsychtoolbox(PsychtoolboxRoot, '601');
> >
> > This will remove context isolation, so if that was the reason,
> > then the demos should work after the downgrade. Of course
> > you will also lose all improvements and bug fixes of the last
> > 5 months and filing any future problem reports for that version
> > is pointless.
> >
> > Do you need 3D graphics support?
> >
> > -mario
>
You don't have the latest driver. This...

<http://www.nvidia.com/object/winxp_169.21_whql.html>

is the latest from Dec. 2007. So download and retry.

I believe i know what's causing the crash and
added some additional error handling for future
betas, but if what i think is causing the crash is
causing the crash, then there isn't any workaround
possible, except NVidia fixing their drivers.

good luck,
-mario

--- In psychtoolbox@yahoogroups.com, Jenny Read <jenny@...> wrote:
>
> Hi Mario, "csabacziraki" et al,
>
> I'm making my first venture into OpenGL with PTB, and have been
> encountering the same problem as "csabacziraki". That is, Matlab crashes
> if I try to open a window after the InitializeMatlabOpenGL command
> (output below). I can get round this by using
> Screen('Preference','ConserveVRAM',8), as you suggested, but I'm
> reluctant to adopt this solution given your dire warnings about the
> nightmare debugging experiences it will lead to!
>
> This is on a PC running Windows XP, 32-bit edition, with an AMD Athlon
> 64 processor 3000+. The graphics card is an NVidia GeForce 8500 GT,
> which as far as I'm aware should be well up to this. I updated PTB today
> and it is 3.0.8 flavour beta, SVN revision 996. I've also updated the
> drivers: it says it was released 5/12/2007 and is version 6.14.11.6921.
> So now I'm scratching my head -- any ideas?
>
> Thanks,
>
> Jenny
>
> Code fragments:
> >>Screen('Preference','ConserveVRAM',8)
> >>InitializeMatlabOpenGL;
> >>[win , winRect] = Screen('OpenWindow', 2, 0,[],[],[], 0, 0, 0);
> works.
> >>InitializeMatlabOpenGL;
> >>[win , winRect] = Screen('OpenWindow', 2, 0,[],[],[], 0, 0, 0);
> (without a previous setting of conserveVram) crashes.
>
> Similarly, all the PTB OpenGL demos work if I first call
> Screen('Preference','ConserveVRAM',8), and crash otherwise.
>
> Here is my test program TestOpenGL2.m
> clear all
> Screen('Preference','Verbosity',6)
> InitializeMatlabOpenGL;
> [win , winRect] = Screen('OpenWindow', 2, 0,[],[],[], 0, 0, 0);
>
> and here is the associated output:
>
> Starting Matlab as Administrator
> TestOpenGL2
> PTB-INFO: Multi-display setup in explicit multi-display mode detected.
> Using the following mapping:
> PTB-INFO: Screen 0 corresponds to the full Windows desktop area. Useful
> for stereo presentations in stereomode=4 ...
> PTB-INFO: Screen 1 corresponds to the display area of the monitor with
> the Windows-internal name \\.\DISPLAY1 ...
> PTB-INFO: Screen 2 corresponds to the display area of the monitor with
> the Windows-internal name \\.\DISPLAY2 ...
> PTB-INFO: Please note that beamposition queries for accurate
> Screen('Flip') timestamping are disabled by
> PTB-INFO: default on MS-Windows multi-display setups. If you want to use
> them, first run the 'PerceptualVBLSyncTest'
> PTB-INFO: script to verify they're working correctly on your setup. Then
> you can add the command:
> PTB-INFO: Screen('Preference', 'VBLTimestampingMode', 1); at the top of
> your script to manually enable them.
> PTB-INFO: Usually beamposition queries work correctly if both of your
> displays are set to the same resolution,
> PTB-INFO: color depths and video refresh rate, but you *must verify this*.
> ans =
> 3
> PTB-INFO: This is the OpenGL-Psychtoolbox for Microsoft Windows, version
> 3.0.8. (Build date: Feb 2 2008)
> PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information.
> PTB-INFO: Psychtoolbox is licensed to you under terms of the GNU General
> Public License (GPL). See file 'License.txt' in the
> PTB-INFO: Psychtoolbox root folder for a copy of the GPL license.
> PTB-INFO: Using GLEW version 1.3.5 for automatic detection of OpenGL
> extensions...
> PTB-DEBUG: Window and master OpenGL context creation finished.
> PTB-DEBUG: Setup of userspace rendering context...
> PTB-DEBUG: wglCreateContext() done. Now copying context state...
> PTB-DEBUG: wglCopyContext() done. Now enabling ressource sharing..
> PTB-DEBUG: Userspace context setup done..
> PTB-DEBUG: Final low-level window setup: ShowWindow(), SetCapture(),
> diagnostics...
> PTB-DEBUG: Final low-level window setup finished. Continuing with
> OS-independent setup.
> OpenGL-Extensions are: (null)
> PTB-DEBUG: Output of all acquired samples of calibration run follows:
> PTB-DEBUG: Sample 0: 0.000000
> PTB-DEBUG: Sample 1: 0.011656
> PTB-DEBUG: Sample 2: 0.017100
> PTB-DEBUG: Sample 3: 0.015756
> PTB-DEBUG: Sample 4: 0.017461
> PTB-DEBUG: Sample 5: 0.016490
> PTB-DEBUG: Sample 6: 0.015433
> PTB-DEBUG: Sample 7: 0.016872
> PTB-DEBUG: Sample 8: 0.016442
> PTB-DEBUG: Sample 9: 0.017173
> PTB-DEBUG: Sample 10: 0.016084
> PTB-DEBUG: Sample 11: 0.016980
> PTB-DEBUG: Sample 12: 0.016449
> PTB-DEBUG: Sample 13: 0.016971
> PTB-DEBUG: Sample 14: 0.016275
> PTB-DEBUG: Sample 15: 0.016899
> PTB-DEBUG: Sample 16: 0.016589
> PTB-DEBUG: Sample 17: 0.016827
> PTB-DEBUG: Sample 18: 0.017217
> PTB-DEBUG: Sample 19: 0.015956
> PTB-DEBUG: Sample 20: 0.016640
> PTB-DEBUG: Sample 21: 0.016521
> PTB-DEBUG: Sample 22: 0.016708
> PTB-DEBUG: Sample 23: 0.016720
> PTB-DEBUG: Sample 24: 0.017011
> PTB-DEBUG: Sample 25: 0.016365
> PTB-DEBUG: Sample 26: 0.016642
> PTB-DEBUG: Sample 27: 0.019863
> PTB-DEBUG: Sample 28: 0.013421
> PTB-DEBUG: Sample 29: 0.016948
> PTB-DEBUG: Sample 30: 0.025074
> PTB-DEBUG: Sample 31: 0.008583
> PTB-DEBUG: Sample 32: 0.016066
> PTB-DEBUG: Sample 33: 0.016675
> PTB-DEBUG: Sample 34: 0.017339
> PTB-DEBUG: Sample 35: 0.015839
> PTB-DEBUG: Sample 36: 0.016729
> PTB-DEBUG: Sample 37: 0.016670
> PTB-DEBUG: Sample 38: 0.016654
> PTB-DEBUG: Sample 39: 0.017430
> PTB-DEBUG: Sample 40: 0.016730
> PTB-DEBUG: Sample 41: 0.015972
> PTB-DEBUG: Sample 42: 0.018012
> PTB-DEBUG: Sample 43: 0.015165
> PTB-DEBUG: Sample 44: 0.016465
> PTB-DEBUG: Sample 45: 0.016653
> PTB-DEBUG: Sample 46: 0.016668
> PTB-DEBUG: Sample 47: 0.016642
> PTB-DEBUG: Sample 48: 0.016671
> PTB-DEBUG: Sample 49: 0.016666
> PTB-DEBUG: Sample 50: 0.016654
> PTB-DEBUG: Sample 51: 0.016663
> PTB-DEBUG: Sample 52: 0.016661
> PTB-DEBUG: Sample 53: 0.016663
> PTB-DEBUG: Sample 54: 0.016667
> PTB-DEBUG: Sample 55: 0.016715
> PTB-DEBUG: Sample 56: 0.016616
> PTB-DEBUG: Sample 57: 0.016658
> PTB-DEBUG: Sample 58: 0.016657
> PTB-DEBUG: Sample 59: 0.016771
> PTB-DEBUG: Sample 60: 0.016561
> PTB-DEBUG: Sample 61: 0.016654
> PTB-DEBUG: Sample 62: 0.016678
> PTB-DEBUG: Sample 63: 0.016657
> PTB-DEBUG: Sample 64: 0.016662
> PTB-DEBUG: Sample 65: 0.016658
> PTB-DEBUG: Sample 66: 0.016663
> PTB-DEBUG: Sample 67: 0.016660
> PTB-DEBUG: Sample 68: 0.016672
> PTB-DEBUG: Sample 69: 0.016664
> PTB-DEBUG: Sample 70: 0.016653
> PTB-DEBUG: Sample 71: 0.016686
> PTB-DEBUG: Sample 72: 0.016645
> PTB-DEBUG: Sample 73: 0.016668
> PTB-DEBUG: Sample 74: 0.016670
> PTB-DEBUG: Sample 75: 0.016659
> PTB-DEBUG: Sample 76: 0.016645
> PTB-DEBUG: Sample 77: 0.016665
> PTB-DEBUG: Sample 78: 0.016660
> PTB-DEBUG: Sample 79: 0.016683
> PTB-DEBUG: Sample 80: 0.016646
> PTB-DEBUG: Sample 81: 0.016663
> PTB-DEBUG: Sample 82: 0.016665
> PTB-DEBUG: Sample 83: 0.016664
> PTB-DEBUG: Sample 84: 0.016658
> PTB-DEBUG: Sample 85: 0.016667
> PTB-DEBUG: Sample 86: 0.016659
> PTB-DEBUG: Sample 87: 0.016663
> PTB-DEBUG: Sample 88: 0.016664
> PTB-DEBUG: Sample 89: 0.016683
> PTB-DEBUG: Sample 90: 0.016646
> PTB-DEBUG: Sample 91: 0.016655
> PTB-DEBUG: Sample 92: 0.016667
> PTB-DEBUG: Sample 93: 0.016658
> PTB-DEBUG: Sample 94: 0.016674
> PTB-DEBUG: Sample 95: 0.016662
> PTB-DEBUG: Sample 96: 0.016660
> PTB-DEBUG: Sample 97: 0.016659
> PTB-DEBUG: Sample 98: 0.017015
> PTB-DEBUG: Sample 99: 0.016332
> PTB-DEBUG: Sample 100: 0.016644
> PTB-DEBUG: Sample 101: 0.016660
> PTB-DEBUG: Sample 102: 0.016700
> PTB-DEBUG: Sample 103: 0.016652
> PTB-DEBUG: Sample 104: 0.016641
> PTB-DEBUG: Sample 105: 0.016660
> PTB-DEBUG: Sample 106: 0.016664
> PTB-DEBUG: Sample 107: 0.016661
> PTB-DEBUG: Sample 108: 0.016668
> PTB-DEBUG: Sample 109: 0.016660
> PTB-DEBUG: Sample 110: 0.016660
> PTB-DEBUG: Sample 111: 0.016664
> PTB-DEBUG: Sample 112: 0.016665
> PTB-DEBUG: Sample 113: 0.016659
> PTB-DEBUG: Sample 114: 0.016661
> PTB-DEBUG: Sample 115: 0.016679
> PTB-DEBUG: Sample 116: 0.016648
> PTB-DEBUG: Sample 117: 0.016684
> PTB-DEBUG: Sample 118: 0.016642
> PTB-DEBUG: Sample 119: 0.016660
> PTB-DEBUG: Sample 120: 0.016665
> PTB-DEBUG: Sample 121: 0.016669
> PTB-DEBUG: Sample 122: 0.016656
> PTB-DEBUG: Sample 123: 0.016662
> PTB-DEBUG: Sample 124: 0.016673
> PTB-DEBUG: Sample 125: 0.016654
> PTB-DEBUG: Sample 126: 0.016663
> PTB-DEBUG: Sample 127: 0.016665
> PTB-DEBUG: Sample 128: 0.016682
> PTB-DEBUG: Sample 129: 0.016647
> PTB-DEBUG: Sample 130: 0.016657
> PTB-DEBUG: Sample 131: 0.016661
> PTB-DEBUG: Sample 132: 0.016683
> PTB-DEBUG: Sample 133: 0.016836
> PTB-DEBUG: Sample 134: 0.016480
> PTB-DEBUG: Sample 135: 0.016654
> PTB-DEBUG: Sample 136: 0.016658
> PTB-DEBUG: Sample 137: 0.016666
> PTB-DEBUG: Sample 138: 0.016659
> PTB-DEBUG: Sample 139: 0.016672
> PTB-DEBUG: Sample 140: 0.016658
> PTB-DEBUG: Sample 141: 0.016670
> PTB-DEBUG: Sample 142: 0.016656
> PTB-DEBUG: Sample 143: 0.016664
> PTB-DEBUG: Sample 144: 0.016663
> PTB-DEBUG: Sample 145: 0.016662
> PTB-DEBUG: Sample 146: 0.016671
> PTB-DEBUG: Sample 147: 0.016655
> PTB-DEBUG: Sample 148: 0.016776
> PTB-DEBUG: Sample 149: 0.016548
> PTB-DEBUG: Sample 150: 0.016663
> PTB-DEBUG: Sample 151: 0.016657
> PTB-DEBUG: Sample 152: 0.016667
> PTB-DEBUG: Sample 153: 0.016657
> PTB-DEBUG: Sample 154: 0.016676
> PTB-DEBUG: Sample 155: 0.016654
> PTB-DEBUG: Sample 156: 0.016660
> PTB-DEBUG: Sample 157: 0.016664
> PTB-DEBUG: Sample 158: 0.016669
> PTB-DEBUG: Sample 159: 0.016671
> PTB-DEBUG: Sample 160: 0.016671
> PTB-DEBUG: Sample 161: 0.016651
> PTB-DEBUG: Sample 162: 0.016691
> PTB-DEBUG: Sample 163: 0.016626
> PTB-DEBUG: Sample 164: 0.016662
> PTB-DEBUG: Sample 165: 0.016664
> PTB-DEBUG: Sample 166: 0.016657
> PTB-DEBUG: Sample 167: 0.016672
> PTB-DEBUG: Sample 168: 0.016655
> PTB-DEBUG: Sample 169: 0.016666
> PTB-DEBUG: Sample 170: 0.016660
> PTB-DEBUG: Sample 171: 0.016660
> PTB-DEBUG: Sample 172: 0.016666
> PTB-DEBUG: Sample 173: 0.016663
> PTB-DEBUG: Sample 174: 0.016669
> PTB-DEBUG: Sample 175: 0.016682
> PTB-DEBUG: Sample 176: 0.016640
> PTB-DEBUG: Sample 177: 0.016665
> PTB-DEBUG: Sample 178: 0.016660
> PTB-DEBUG: Sample 179: 0.016659
> PTB-DEBUG: Sample 180: 0.016674
> PTB-DEBUG: Sample 181: 0.016648
> PTB-DEBUG: Sample 182: 0.016668
> PTB-DEBUG: Sample 183: 0.016657
> PTB-DEBUG: Sample 184: 0.016673
> PTB-DEBUG: Sample 185: 0.016657
> PTB-DEBUG: Sample 186: 0.016662
> PTB-DEBUG: Sample 187: 0.016665
> PTB-DEBUG: Sample 188: 0.016670
> PTB-DEBUG: Sample 189: 0.016667
> PTB-DEBUG: Sample 190: 0.016649
> PTB-DEBUG: Sample 191: 0.016662
> PTB-DEBUG: Sample 192: 0.016663
> PTB-DEBUG: Sample 193: 0.016676
> PTB-DEBUG: Sample 194: 0.016668
> PTB-DEBUG: Sample 195: 0.016651
> PTB-DEBUG: Sample 196: 0.016653
> PTB-DEBUG: Sample 197: 0.016666
> PTB-DEBUG: Sample 198: 0.016658
> PTB-DEBUG: Sample 199: 0.016671
> PTB-DEBUG: Sample 200: 0.016668
> PTB-DEBUG: Sample 201: 0.016652
> PTB-DEBUG: Sample 202: 0.016662
> PTB-DEBUG: Sample 203: 0.016688
> PTB-DEBUG: Sample 204: 0.016640
> PTB-DEBUG: Sample 205: 0.016660
> PTB-DEBUG: Sample 206: 0.016664
> PTB-DEBUG: Sample 207: 0.016666
> PTB-DEBUG: Sample 208: 0.016658
> PTB-DEBUG: Sample 209: 0.016665
> PTB-DEBUG: Sample 210: 0.016666
> PTB-DEBUG: Sample 211: 0.016657
> PTB-DEBUG: Sample 212: 0.016666
> PTB-DEBUG: Sample 213: 0.016665
> PTB-DEBUG: Sample 214: 0.016659
> PTB-DEBUG: Sample 215: 0.016660
> PTB-DEBUG: Sample 216: 0.016662
> PTB-DEBUG: Sample 217: 0.016663
> PTB-DEBUG: Sample 218: 0.016693
> PTB-DEBUG: Sample 219: 0.016637
> PTB-DEBUG: Sample 220: 0.016678
> PTB-DEBUG: Sample 221: 0.016646
> PTB-DEBUG: Sample 222: 0.016688
> PTB-DEBUG: Sample 223: 0.016641
> PTB-DEBUG: Sample 224: 0.016661
> PTB-DEBUG: Sample 225: 0.016664
> PTB-DEBUG: Sample 226: 0.016656
> PTB-DEBUG: Sample 227: 0.016681
> PTB-DEBUG: Sample 228: 0.016650
> PTB-DEBUG: Sample 229: 0.016674
> PTB-DEBUG: Sample 230: 0.016695
> PTB-DEBUG: Sample 231: 0.016619
> PTB-DEBUG: Sample 232: 0.016682
> PTB-DEBUG: Sample 233: 0.016648
> PTB-DEBUG: Sample 234: 0.016659
> PTB-DEBUG: Sample 235: 0.016662
> PTB-DEBUG: Sample 236: 0.016658
> PTB-DEBUG: Sample 237: 0.016670
> PTB-DEBUG: Sample 238: 0.016655
> PTB-DEBUG: Sample 239: 0.016672
> PTB-DEBUG: Sample 240: 0.016659
> PTB-DEBUG: Sample 241: 0.016655
> PTB-DEBUG: Sample 242: 0.016771
> PTB-DEBUG: Sample 243: 0.016563
> PTB-DEBUG: Sample 244: 0.016682
> PTB-DEBUG: Sample 245: 0.016642
> PTB-DEBUG: Sample 246: 0.016687
> PTB-DEBUG: Sample 247: 0.016636
> PTB-DEBUG: Sample 248: 0.016668
> PTB-DEBUG: Sample 249: 0.016660
> PTB-DEBUG: Sample 250: 0.016667
> PTB-DEBUG: Sample 251: 0.016654
> PTB-DEBUG: Sample 252: 0.016667
> PTB-DEBUG: Sample 253: 0.016679
> PTB-DEBUG: Sample 254: 0.016644
> PTB-DEBUG: Sample 255: 0.016662
> PTB-DEBUG: Sample 256: 0.016657
> PTB-DEBUG: Sample 257: 0.016666
> PTB-DEBUG: Sample 258: 0.016660
> PTB-DEBUG: Sample 259: 0.016673
> PTB-DEBUG: Sample 260: 0.016661
> PTB-DEBUG: Sample 261: 0.016685
> PTB-DEBUG: Sample 262: 0.016638
> PTB-DEBUG: Sample 263: 0.016685
> PTB-DEBUG: Sample 264: 0.016641
> PTB-DEBUG: Sample 265: 0.016661
> PTB-DEBUG: Sample 266: 0.016665
> PTB-DEBUG: Sample 267: 0.016660
> PTB-DEBUG: Sample 268: 0.016662
> PTB-DEBUG: Sample 269: 0.016662
> PTB-DEBUG: Sample 270: 0.016664
> PTB-DEBUG: Sample 271: 0.016656
> PTB-DEBUG: Sample 272: 0.016666
> PTB-DEBUG: Sample 273: 0.016668
> PTB-DEBUG: Sample 274: 0.016660
> PTB-DEBUG: Sample 275: 0.016676
> PTB-DEBUG: Sample 276: 0.016653
> PTB-DEBUG: Sample 277: 0.016660
> PTB-DEBUG: Sample 278: 0.016669
> PTB-DEBUG: Sample 279: 0.016661
> PTB-DEBUG: Sample 280: 0.016655
> PTB-DEBUG: Sample 281: 0.016676
> PTB-DEBUG: Sample 282: 0.016679
> PTB-DEBUG: Sample 283: 0.016633
> PTB-DEBUG: Sample 284: 0.016664
> PTB-DEBUG: Sample 285: 0.016674
> PTB-DEBUG: Sample 286: 0.016647
> PTB-DEBUG: Sample 287: 0.016666
> PTB-DEBUG: Sample 288: 0.016660
> PTB-DEBUG: Sample 289: 0.016669
> PTB-DEBUG: Sample 290: 0.016678
> PTB-DEBUG: Sample 291: 0.016649
> PTB-DEBUG: Sample 292: 0.016664
> PTB-DEBUG: Sample 293: 0.016663
> PTB-DEBUG: Sample 294: 0.016661
> PTB-DEBUG: Sample 295: 0.016664
> PTB-DEBUG: Sample 296: 0.016660
> PTB-DEBUG: Sample 297: 0.016661
> PTB-DEBUG: Sample 298: 0.016666
> PTB-DEBUG: Sample 299: 0.016664
> PTB-DEBUG: End of calibration data for this run...
> Saving minidump to file
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\matlab_crash_dump.3696.0.dmp
> -------------------------------------------------------------------
-----
> Segmentation violation detected at Thu Mar 20 16:49:00 2008
> -------------------------------------------------------------------
-----
> Configuration:
> MATLAB Version: 7.5.0.342 (R2007b)
> MATLAB License: 303224
> Operating System: Microsoft Windows XP
> Window System: Version 5.1 (Build 2600: Service Pack 2)
> Processor ID: x86 Family 15 Model 12 Stepping 2, AuthenticAMD
> Virtual Machine: Java 1.6.0 with Sun Microsystems Inc. Java
> HotSpot(TM) Client VM mixed mode
> Default Charset: windows-1252
> Register State:
> EAX = 00000000 EBX = 78144e50
> ECX = 139df930 EDX = 00076e49
> ESI = 00000000 EDI = 00000000
> EBP = 00cecce8 ESP = 00cecc3c
> EIP = 78144e6e FLG = 00010202
> Stack Trace:
> [0] MSVCR80.dll:0x78144e6e(0x00cecd20, 0x00ceced0, 2, 0)
> [1] Screen.dll:0x139b8c7a(0x00ced7fc, 2464, 257, 0)
> [2] Screen.dll:0x139a74d2(2, 0x00ced7fc, 9, 0x00ced88c)
> [3] libmex.dll:_mexRunMexFile(2, 0x00ced7fc, 9, 0x00ced88c) + 139 bytes
> [4] libmex.dll:private: void __thiscall
> Mfh_mex::runMexFileWithSignalProtection(int,struct mxArray_tag *
> *,int,struct mxArray_tag * *)(2, 0x00ced7fc, 9, 0x00ced88c) + 86 bytes
> [5] libmex.dll:public: virtual void __thiscall
> Mfh_mex::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag
> * *)(2, 0x00ced7fc, 9, 0x00ced88c) + 261 bytes
> [6] m_dispatcher.dll:public: virtual void __thiscall
> Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag
> * *)(2, 0x00ced7fc, 9, 0x00ced88c) + 203 bytes
> [7] m_interpreter.dll:void __cdecl mdCallFunction(int,struct
> mxArray_tag * *,int,struct mxArray_tag * *,class Mfh_MATLAB_fn *)(2,
> 0x00ced7fc, 9, 0x00ced88c) + 56 bytes
> [8] m_interpreter.dll:public: void __thiscall
> ResolverFunctionDesc::CallFunction(int,struct mxArray_tag * *
> const,int,struct mxArray_tag * * const)(2, 0x00ced7fc, 9, 0x00ced88c) +
> 93 bytes
> [9] m_interpreter.dll:public: bool __thiscall
> Resolver::CallMFunction(int,int,class _m_operand * const,union
> m_operand_storage *,int,class _m_operand * const,union m_operand_storage
> *,int *)(2, 2, 0x01569fa0, 0) + 1388 bytes
> [10] m_interpreter.dll:bool __cdecl inResolveMFunctionCall(struct
> _m_function_desc *,int,int,class _m_operand * const,union
> m_operand_storage *,int,class _m_operand * const,union m_operand_storage
> *,int *,enum inMarshalType *,int,class mpsTypeSequenceNlhs const
> *,struct mxArray_tag * (__cdecl*)(int))(0x126b6638, 2, 2, 0x01569fa0) +
> 195 bytes
> [11] m_interpreter.dll:private: bool __thiscall
> accelImpl::MFunctionCall(struct _accelOp * *)(0x00cede98, 0xee6c3d7c,
> 0x03825ea0, 0x5cc05610) + 179 bytes
> [12] m_interpreter.dll:public: enum jitReturnFlags __thiscall
> accelImpl::Exec(void)(0xee6c3de4, 0x03825ea0, 1, 0x00cee24c) + 205 bytes
> [13] m_interpreter.dll:public: enum jitReturnFlags __thiscall
> accelCode::Call(enum inMarshalType *,int *)const (0x00cedf9c,
> 0x00cedf74, 0xee6c3ca8, 0) + 128 bytes
> [14] m_interpreter.dll:public: static bool __cdecl
> inJit::ExecuteHotSegment(struct _inJitAccelInfo *,enum opcodes *,int
> *,int *)(0x00cee044, 0x00cee0f8, 0x00cee0a8, 0x00cee24c) + 1898 bytes
> [15] m_interpreter.dll:int __cdecl inInterp(enum
> inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *,int
> *)(1, 0, 3, 0) + 338 bytes
> [16] m_interpreter.dll:int __cdecl protected_inInterp(enum
> inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(1, 0,
> 1, 0) + 87 bytes
> [17] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum
> inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(1, 0,
> 1, 0) + 274 bytes
> [18] m_interpreter.dll:int __cdecl inExecuteMFunctionOrScript(class
> Mfh_mp *,bool)(0x03876220 "D#ùy÷A", 0x03832201, 0xee6c0710, 0xffffffff)
> + 916 bytes
> [19] m_interpreter.dll:void __cdecl inRunMfile(int,struct mxArray_tag
> * *,int,struct mxArray_tag * *,class Mfh_mp *,struct inWorkSpace_tag
> *)(0, 0x00cee4c4, 0, 0x00cee524) + 673 bytes
> [20] m_interpreter.dll:public: virtual void __thiscall
> Mfh_mp::dispatch_file(struct _mdUnknown_workspace *,int,struct
> mxArray_tag * *,int,struct mxArray_tag * *)(0, 0, 0x00cee4c4, 0) + 29 bytes
> [21] m_interpreter.dll:public: virtual void __thiscall
> Mfh_mp::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag
> * *)(0, 0x00cee4c4, 0, 0x00cee524) + 28 bytes
> [22] m_dispatcher.dll:public: virtual void __thiscall
> Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag
> * *)(0, 0x00cee4c4, 0, 0x00cee524) + 203 bytes
> [23]
> m_interpreter.dll:__catch$?inDispatchFromStack@@YAHHPBDHH@Z$0(602,
> 0x01580304 "TestOpenGL2", 0, 0) + 744 bytes
> [24] m_interpreter.dll:enum opcodes __cdecl inDispatchCall(char const
> *,int,int,int,int *,int *)(0x01580304 "TestOpenGL2", 602, 0, 0) + 156 bytes
> [25] m_interpreter.dll:int __cdecl inInterp(enum
> inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *,int
> *)(2, 0, 0, 0) + 2739 bytes
> [26] m_interpreter.dll:int __cdecl protected_inInterp(enum
> inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(2, 0,
> 0, 0) + 87 bytes
> [27] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum
> inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(2, 0,
> 0, 0) + 274 bytes
> [28] m_interpreter.dll:_inInterPcode(2, 0xee6c0be8, 0, 0x038c8820
> "TestOpenGL2\n") + 162 bytes
> [29] m_interpreter.dll:enum inExecutionStatus __cdecl
> in_local_call_eval_function(int *,struct _pcodeheader *,int *,struct
> mxArray_tag * * const,enum inDebugCheck,bool)(0x00cef2bc, 0x00cef32c,
> 0x00cef358, 2) + 152 bytes
> [30] m_interpreter.dll:enum inExecutionStatus __cdecl
> inEvalStringWithIsVarFcn(struct _memory_context *,char const *,enum
> EvalType,int,struct mxArray_tag * * const,enum inDebugCheck,struct
> _pcodeheader *,int *,bool (__cdecl*)(void *,char const *),void
> *,bool)(0x7ac2177c, 0x038c8820 "TestOpenGL2\n", 0, 0) + 2454 bytes
> [31] m_interpreter.dll:enum inExecutionStatus __cdecl
> inEvalCmdWithLocalReturnandtype(char const *,int *,enum
> inDebugCheck,bool)(0x038c8820 "TestOpenGL2\n", 0, 2, 0) + 107 bytes
> [32] m_interpreter.dll:_inEvalCmdNoEnd(0x038c8820 "TestOpenGL2\n", 0,
> 0xee4b5dc0, 0x7ab9e7f0) + 20 bytes
> [33] bridge.dll:enum inExecutionStatus __cdecl ThrowSignal(char const
> *)(0x038c8820 "TestOpenGL2\n", 0xee4b5a8c, 0x01483fd0, 0x01483f70) + 77
> bytes
> [34] bridge.dll:__catch$_mnParser$0(0xee571969, 0x01483f70,
> 0x01483f70, 0) + 292 bytes
> [35] mcr.dll:public: void __thiscall
> mcrInstance::mnParser(void)(0xee571149, 0x004043f0, 336710, 0) + 62 bytes
> [36] MATLAB.exe:0x00401414(4194304, 0, 336710, 10)
> [37] MATLAB.exe:0x00401733(0, 0, 0x7ffdd000, 0x80543ffd)
> [38] kernel32.dll:0x7c816fd7(0x00401910, 0, 0x78746341, 32)
> This error was detected while a MEX-file was running. If the MEX-file
> is not an official MathWorks function, please examine its source code
> for errors. Please consult the External Interfaces Guide for information
> on debugging MEX-files.
> If it is an official MathWorks function, please
> follow these steps to report this problem to The MathWorks so we
> have the best chance of correcting it:
> The next time MATLAB is launched under typical usage, a dialog box will
> open to help you send the error log to The MathWorks. Alternatively, you
> can send an e-mail to segv@... with the following file attached:
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\matlab_crash_dump.3696
> If the problem is reproducible, please submit a Service Request via:
> http://www.mathworks.com/support/contact_us/ts/help_request_1.html
> A technical support engineer might contact you with further information.
> Thank you for your help. Save your workspace and restart MATLAB.
>
>
>
> Mario Kleiner wrote:
> >
> > Ok, workaround included in current PTB beta. UpdatePsychtoolbox to
> > get the latest beta release. Then try two things:
> >
> > 1. Screen('Preference', 'Verbosity', 6);
> > Run OpenGL demo again, post the Matlab output. The debug output
> > should allow to narrow down the faulty driver command. Maybe
> > we can provide a more focused workaround in the future, based on
> > that information.
> >
> > 2. In the future, add a Screen('Preference', 'ConserveVRAM', 8); to
> > the top of your OpenGL scripts to disable context isolation.
> >
> > -mario
> >
> > --- In psychtoolbox@yahoogroups.com
> > <mailto:psychtoolbox%40yahoogroups.com>, "csabacziraki"
> > <csabacziraki@> wrote:
> > >
> > > Thanks a lot for your help!
> > >
> > > --- In psychtoolbox@yahoogroups.com
> > <mailto:psychtoolbox%40yahoogroups.com>, "Mario Kleiner"
> > > <mario.kleiner@> wrote:
> > > >
> > > > Jap. The problem is that ACER doesn't design their notebooks
> > > > in a compliant fashion so they need these customized drivers
> > > > and that they don't care too much about customer support,
> > > > otherwise they would at least provide half-yearly
> > > > updates of their drivers.
> > > >
> > > > So the best solution for ACERs bug would be to ask them to
> > > > provide a driver update. Your gfx-card will also be incapable
> > > > of supporting any of the new features of PTB although the
> > > > hardware can do it, just insufficient outdated drivers.
> > > >
> > > > And its probably a good idea for Windows users to check the
> > > > webpages of graphcis vendors like ATI or NVidia before they
> > > > buy a portable and prefer a vendor that allows use of the
> > > > generic drivers - that way at least you get timely driver
> > > > updates.
> > > >
> > > > The next beta release will contain a switch to disable context
> > > > isolation for such broken systems. Then PTB will work with
> > > > OpenGL, but without the additional protection layer: Much
> > > > more time spent for you to hunt down bugs in your own
> > > > OpenGL code or finding unwanted interactions with PTB, not
> > > > fun at all. I already spent a workday on hunting such ghosts
> > > > in my own experiment code -- and i'm at a big advantage
> > > > knowing how everything works, so good luck for you if you
> > > > hit such a problem.
> > > >
> > > > -mario
> > >
> >
> >
>
Ah ok,

can anybody else (or you) verify how this behaves
on other NVidia hardware or with other driver
versions? Maybe its a specific driver release where
the bug was introduced.

Other things to test (all with a high verbosity level,
ie. Screen('Preference','Verbosity', 10);)

All without the 'ConserveVRAM', 8) workaround
applied!

MinimalisticOpenGLDemo(0) vs.
MinimalisticOpenGLDemo(1)
Any difference in crashing behaviour or how
far it gets before dying?

And what happens if you run in windowed
mode, ie., setting the 'rect' parameter to some
say [0 0 400 400]? e.g.,

win = Screen('OpenWindow', 0, 0, [0 0 400 400]);

--> The position in the startup sequence where
it aborts with a crash allows to narrow down,
where the crash happens in the code.

--> Simply post the Matlab output for the
different cases.

The good news is that since yesterday i have
access to NVidias bugreporting and technical
developer support, after many months of
struggling to get that privilege. So now we
can submit bugreports for NVidia
drivers if we happen to find some. Its of
course still up to NVidias priority list if our
bugs are important enough compared to
other peoples bugs, but this is much better
than just hoping for the best or relying on
their mind-reading skills ;-)

best,
-mario


--- In psychtoolbox@yahoogroups.com, Jenny Read <J.C.A.Read@...> wrote:
>
> Mario Kleiner wrote:
> >
> > You don't have the latest driver. This...
> >
> > <http://www.nvidia.com/object/winxp_169.21_whql.html
> > <http://www.nvidia.com/object/winxp_169.21_whql.html>>
> >
> > is the latest from Dec. 2007. So download and retry.
> >
>
>
>
>
>
> Sorry, I wasn't clear -- that is the file I used. If you install that,
> the resulting driver is version 6.14.11.6921 released 5/12/2007. This
> puzzled me, but according to my PhD student Graeme Phillipson, who knows
> more about such matters than me, it's because "Nvidia put all drivers
> for all cards together in one file, with its own version number separate
> from the version number for any individual driver. So if Nvidia release
> a new card (9500 GT say) tomorrow the graphics driver version on their
> website will go to 170, but if you install version 170, you will still
> see version 6.14... as your actual graphics driver because you only have
> a 8500 GT. "
>
>
> >
> > I believe i know what's causing the crash and
> > added some additional error handling for future
> > betas, but if what i think is causing the crash is
> > causing the crash, then there isn't any workaround
> > possible, except NVidia fixing their drivers.
> >
>
>
>
>
>
>
> Ah, OK. Thanks for looking into it; I'll keep an eye out for any new
> NVidia releases and see if they fix it. The good news is, the
> ConserveVRAM workaround doesn't seem to be causing any problems.
> Admittedly I'm creating a very simple stimulus, but so far it all seems
> to be working without getting me into any horrendous debugging quagmire.
>
> Many thanks again,
>
> Jenny
>
> (about to have another go at the Cedrus...!)
>
> >
> > good luck,
> > -mario
> >
> > --- In psychtoolbox@yahoogroups.com
> > <mailto:psychtoolbox%40yahoogroups.com>, Jenny Read <jenny@> wrote:
> > >
> > > Hi Mario, "csabacziraki" et al,
> > >
> > > I'm making my first venture into OpenGL with PTB, and have been
> > > encountering the same problem as "csabacziraki". That is, Matlab
> > crashes
> > > if I try to open a window after the InitializeMatlabOpenGL command
> > > (output below). I can get round this by using
> > > Screen('Preference','ConserveVRAM',8), as you suggested, but I'm
> > > reluctant to adopt this solution given your dire warnings about the
> > > nightmare debugging experiences it will lead to!
> > >
> > > This is on a PC running Windows XP, 32-bit edition, with an AMD Athlon
> > > 64 processor 3000+. The graphics card is an NVidia GeForce 8500 GT,
> > > which as far as I'm aware should be well up to this. I updated PTB
> > today
> > > and it is 3.0.8 flavour beta, SVN revision 996. I've also updated the
> > > drivers: it says it was released 5/12/2007 and is version 6.14.11.6921.
> > > So now I'm scratching my head -- any ideas?
> > >
> > > Thanks,
> > >
> > > Jenny
> > >
> > > Code fragments:
> > > >>Screen('Preference','ConserveVRAM',8)
> > > >>InitializeMatlabOpenGL;
> > > >>[win , winRect] = Screen('OpenWindow', 2, 0,[],[],[], 0, 0, 0);
> > > works.
> > > >>InitializeMatlabOpenGL;
> > > >>[win , winRect] = Screen('OpenWindow', 2, 0,[],[],[], 0, 0, 0);
> > > (without a previous setting of conserveVram) crashes.
> > >
> > > Similarly, all the PTB OpenGL demos work if I first call
> > > Screen('Preference','ConserveVRAM',8), and crash otherwise.
> > >
> > > Here is my test program TestOpenGL2.m
> > > clear all
> > > Screen('Preference','Verbosity',6)
> > > InitializeMatlabOpenGL;
> > > [win , winRect] = Screen('OpenWindow', 2, 0,[],[],[], 0, 0, 0);
> > >
> > > and here is the associated output:
> > >
> > > Starting Matlab as Administrator
> > > TestOpenGL2
> > > PTB-INFO: Multi-display setup in explicit multi-display mode detected.
> > > Using the following mapping:
> > > PTB-INFO: Screen 0 corresponds to the full Windows desktop area. Useful
> > > for stereo presentations in stereomode=4 ...
> > > PTB-INFO: Screen 1 corresponds to the display area of the monitor with
> > > the Windows-internal name \\.\DISPLAY1 ...
> > > PTB-INFO: Screen 2 corresponds to the display area of the monitor with
> > > the Windows-internal name \\.\DISPLAY2 ...
> > > PTB-INFO: Please note that beamposition queries for accurate
> > > Screen('Flip') timestamping are disabled by
> > > PTB-INFO: default on MS-Windows multi-display setups. If you want to
> > use
> > > them, first run the 'PerceptualVBLSyncTest'
> > > PTB-INFO: script to verify they're working correctly on your setup.
> > Then
> > > you can add the command:
> > > PTB-INFO: Screen('Preference', 'VBLTimestampingMode', 1); at the top of
> > > your script to manually enable them.
> > > PTB-INFO: Usually beamposition queries work correctly if both of your
> > > displays are set to the same resolution,
> > > PTB-INFO: color depths and video refresh rate, but you *must verify
> > this*.
> > > ans =
> > > 3
> > > PTB-INFO: This is the OpenGL-Psychtoolbox for Microsoft Windows,
> > version
> > > 3.0.8. (Build date: Feb 2 2008)
> > > PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version
> > information.
> > > PTB-INFO: Psychtoolbox is licensed to you under terms of the GNU
> > General
> > > Public License (GPL). See file 'License.txt' in the
> > > PTB-INFO: Psychtoolbox root folder for a copy of the GPL license.
> > > PTB-INFO: Using GLEW version 1.3.5 for automatic detection of OpenGL
> > > extensions...
> > > PTB-DEBUG: Window and master OpenGL context creation finished.
> > > PTB-DEBUG: Setup of userspace rendering context...
> > > PTB-DEBUG: wglCreateContext() done. Now copying context state...
> > > PTB-DEBUG: wglCopyContext() done. Now enabling ressource sharing..
> > > PTB-DEBUG: Userspace context setup done..
> > > PTB-DEBUG: Final low-level window setup: ShowWindow(), SetCapture(),
> > > diagnostics...
> > > PTB-DEBUG: Final low-level window setup finished. Continuing with
> > > OS-independent setup.
> > > OpenGL-Extensions are: (null)
> > > PTB-DEBUG: Output of all acquired samples of calibration run follows:
> > > PTB-DEBUG: Sample 0: 0.000000
> > > PTB-DEBUG: Sample 1: 0.011656
> > > PTB-DEBUG: Sample 2: 0.017100
> > > PTB-DEBUG: Sample 3: 0.015756
> > > PTB-DEBUG: Sample 4: 0.017461
> > > PTB-DEBUG: Sample 5: 0.016490
> > > PTB-DEBUG: Sample 6: 0.015433
> > > PTB-DEBUG: Sample 7: 0.016872
> > > PTB-DEBUG: Sample 8: 0.016442
> > > PTB-DEBUG: Sample 9: 0.017173
> > > PTB-DEBUG: Sample 10: 0.016084
> > > PTB-DEBUG: Sample 11: 0.016980
> > > PTB-DEBUG: Sample 12: 0.016449
> > > PTB-DEBUG: Sample 13: 0.016971
> > > PTB-DEBUG: Sample 14: 0.016275
> > > PTB-DEBUG: Sample 15: 0.016899
> > > PTB-DEBUG: Sample 16: 0.016589
> > > PTB-DEBUG: Sample 17: 0.016827
> > > PTB-DEBUG: Sample 18: 0.017217
> > > PTB-DEBUG: Sample 19: 0.015956
> > > PTB-DEBUG: Sample 20: 0.016640
> > > PTB-DEBUG: Sample 21: 0.016521
> > > PTB-DEBUG: Sample 22: 0.016708
> > > PTB-DEBUG: Sample 23: 0.016720
> > > PTB-DEBUG: Sample 24: 0.017011
> > > PTB-DEBUG: Sample 25: 0.016365
> > > PTB-DEBUG: Sample 26: 0.016642
> > > PTB-DEBUG: Sample 27: 0.019863
> > > PTB-DEBUG: Sample 28: 0.013421
> > > PTB-DEBUG: Sample 29: 0.016948
> > > PTB-DEBUG: Sample 30: 0.025074
> > > PTB-DEBUG: Sample 31: 0.008583
> > > PTB-DEBUG: Sample 32: 0.016066
> > > PTB-DEBUG: Sample 33: 0.016675
> > > PTB-DEBUG: Sample 34: 0.017339
> > > PTB-DEBUG: Sample 35: 0.015839
> > > PTB-DEBUG: Sample 36: 0.016729
> > > PTB-DEBUG: Sample 37: 0.016670
> > > PTB-DEBUG: Sample 38: 0.016654
> > > PTB-DEBUG: Sample 39: 0.017430
> > > PTB-DEBUG: Sample 40: 0.016730
> > > PTB-DEBUG: Sample 41: 0.015972
> > > PTB-DEBUG: Sample 42: 0.018012
> > > PTB-DEBUG: Sample 43: 0.015165
> > > PTB-DEBUG: Sample 44: 0.016465
> > > PTB-DEBUG: Sample 45: 0.016653
> > > PTB-DEBUG: Sample 46: 0.016668
> > > PTB-DEBUG: Sample 47: 0.016642
> > > PTB-DEBUG: Sample 48: 0.016671
> > > PTB-DEBUG: Sample 49: 0.016666
> > > PTB-DEBUG: Sample 50: 0.016654
> > > PTB-DEBUG: Sample 51: 0.016663
> > > PTB-DEBUG: Sample 52: 0.016661
> > > PTB-DEBUG: Sample 53: 0.016663
> > > PTB-DEBUG: Sample 54: 0.016667
> > > PTB-DEBUG: Sample 55: 0.016715
> > > PTB-DEBUG: Sample 56: 0.016616
> > > PTB-DEBUG: Sample 57: 0.016658
> > > PTB-DEBUG: Sample 58: 0.016657
> > > PTB-DEBUG: Sample 59: 0.016771
> > > PTB-DEBUG: Sample 60: 0.016561
> > > PTB-DEBUG: Sample 61: 0.016654
> > > PTB-DEBUG: Sample 62: 0.016678
> > > PTB-DEBUG: Sample 63: 0.016657
> > > PTB-DEBUG: Sample 64: 0.016662
> > > PTB-DEBUG: Sample 65: 0.016658
> > > PTB-DEBUG: Sample 66: 0.016663
> > > PTB-DEBUG: Sample 67: 0.016660
> > > PTB-DEBUG: Sample 68: 0.016672
> > > PTB-DEBUG: Sample 69: 0.016664
> > > PTB-DEBUG: Sample 70: 0.016653
> > > PTB-DEBUG: Sample 71: 0.016686
> > > PTB-DEBUG: Sample 72: 0.016645
> > > PTB-DEBUG: Sample 73: 0.016668
> > > PTB-DEBUG: Sample 74: 0.016670
> > > PTB-DEBUG: Sample 75: 0.016659
> > > PTB-DEBUG: Sample 76: 0.016645
> > > PTB-DEBUG: Sample 77: 0.016665
> > > PTB-DEBUG: Sample 78: 0.016660
> > > PTB-DEBUG: Sample 79: 0.016683
> > > PTB-DEBUG: Sample 80: 0.016646
> > > PTB-DEBUG: Sample 81: 0.016663
> > > PTB-DEBUG: Sample 82: 0.016665
> > > PTB-DEBUG: Sample 83: 0.016664
> > > PTB-DEBUG: Sample 84: 0.016658
> > > PTB-DEBUG: Sample 85: 0.016667
> > > PTB-DEBUG: Sample 86: 0.016659
> > > PTB-DEBUG: Sample 87: 0.016663
> > > PTB-DEBUG: Sample 88: 0.016664
> > > PTB-DEBUG: Sample 89: 0.016683
> > > PTB-DEBUG: Sample 90: 0.016646
> > > PTB-DEBUG: Sample 91: 0.016655
> > > PTB-DEBUG: Sample 92: 0.016667
> > > PTB-DEBUG: Sample 93: 0.016658
> > > PTB-DEBUG: Sample 94: 0.016674
> > > PTB-DEBUG: Sample 95: 0.016662
> > > PTB-DEBUG: Sample 96: 0.016660
> > > PTB-DEBUG: Sample 97: 0.016659
> > > PTB-DEBUG: Sample 98: 0.017015
> > > PTB-DEBUG: Sample 99: 0.016332
> > > PTB-DEBUG: Sample 100: 0.016644
> > > PTB-DEBUG: Sample 101: 0.016660
> > > PTB-DEBUG: Sample 102: 0.016700
> > > PTB-DEBUG: Sample 103: 0.016652
> > > PTB-DEBUG: Sample 104: 0.016641
> > > PTB-DEBUG: Sample 105: 0.016660
> > > PTB-DEBUG: Sample 106: 0.016664
> > > PTB-DEBUG: Sample 107: 0.016661
> > > PTB-DEBUG: Sample 108: 0.016668
> > > PTB-DEBUG: Sample 109: 0.016660
> > > PTB-DEBUG: Sample 110: 0.016660
> > > PTB-DEBUG: Sample 111: 0.016664
> > > PTB-DEBUG: Sample 112: 0.016665
> > > PTB-DEBUG: Sample 113: 0.016659
> > > PTB-DEBUG: Sample 114: 0.016661
> > > PTB-DEBUG: Sample 115: 0.016679
> > > PTB-DEBUG: Sample 116: 0.016648
> > > PTB-DEBUG: Sample 117: 0.016684
> > > PTB-DEBUG: Sample 118: 0.016642
> > > PTB-DEBUG: Sample 119: 0.016660
> > > PTB-DEBUG: Sample 120: 0.016665
> > > PTB-DEBUG: Sample 121: 0.016669
> > > PTB-DEBUG: Sample 122: 0.016656
> > > PTB-DEBUG: Sample 123: 0.016662
> > > PTB-DEBUG: Sample 124: 0.016673
> > > PTB-DEBUG: Sample 125: 0.016654
> > > PTB-DEBUG: Sample 126: 0.016663
> > > PTB-DEBUG: Sample 127: 0.016665
> > > PTB-DEBUG: Sample 128: 0.016682
> > > PTB-DEBUG: Sample 129: 0.016647
> > > PTB-DEBUG: Sample 130: 0.016657
> > > PTB-DEBUG: Sample 131: 0.016661
> > > PTB-DEBUG: Sample 132: 0.016683
> > > PTB-DEBUG: Sample 133: 0.016836
> > > PTB-DEBUG: Sample 134: 0.016480
> > > PTB-DEBUG: Sample 135: 0.016654
> > > PTB-DEBUG: Sample 136: 0.016658
> > > PTB-DEBUG: Sample 137: 0.016666
> > > PTB-DEBUG: Sample 138: 0.016659
> > > PTB-DEBUG: Sample 139: 0.016672
> > > PTB-DEBUG: Sample 140: 0.016658
> > > PTB-DEBUG: Sample 141: 0.016670
> > > PTB-DEBUG: Sample 142: 0.016656
> > > PTB-DEBUG: Sample 143: 0.016664
> > > PTB-DEBUG: Sample 144: 0.016663
> > > PTB-DEBUG: Sample 145: 0.016662
> > > PTB-DEBUG: Sample 146: 0.016671
> > > PTB-DEBUG: Sample 147: 0.016655
> > > PTB-DEBUG: Sample 148: 0.016776
> > > PTB-DEBUG: Sample 149: 0.016548
> > > PTB-DEBUG: Sample 150: 0.016663
> > > PTB-DEBUG: Sample 151: 0.016657
> > > PTB-DEBUG: Sample 152: 0.016667
> > > PTB-DEBUG: Sample 153: 0.016657
> > > PTB-DEBUG: Sample 154: 0.016676
> > > PTB-DEBUG: Sample 155: 0.016654
> > > PTB-DEBUG: Sample 156: 0.016660
> > > PTB-DEBUG: Sample 157: 0.016664
> > > PTB-DEBUG: Sample 158: 0.016669
> > > PTB-DEBUG: Sample 159: 0.016671
> > > PTB-DEBUG: Sample 160: 0.016671
> > > PTB-DEBUG: Sample 161: 0.016651
> > > PTB-DEBUG: Sample 162: 0.016691
> > > PTB-DEBUG: Sample 163: 0.016626
> > > PTB-DEBUG: Sample 164: 0.016662
> > > PTB-DEBUG: Sample 165: 0.016664
> > > PTB-DEBUG: Sample 166: 0.016657
> > > PTB-DEBUG: Sample 167: 0.016672
> > > PTB-DEBUG: Sample 168: 0.016655
> > > PTB-DEBUG: Sample 169: 0.016666
> > > PTB-DEBUG: Sample 170: 0.016660
> > > PTB-DEBUG: Sample 171: 0.016660
> > > PTB-DEBUG: Sample 172: 0.016666
> > > PTB-DEBUG: Sample 173: 0.016663
> > > PTB-DEBUG: Sample 174: 0.016669
> > > PTB-DEBUG: Sample 175: 0.016682
> > > PTB-DEBUG: Sample 176: 0.016640
> > > PTB-DEBUG: Sample 177: 0.016665
> > > PTB-DEBUG: Sample 178: 0.016660
> > > PTB-DEBUG: Sample 179: 0.016659
> > > PTB-DEBUG: Sample 180: 0.016674
> > > PTB-DEBUG: Sample 181: 0.016648
> > > PTB-DEBUG: Sample 182: 0.016668
> > > PTB-DEBUG: Sample 183: 0.016657
> > > PTB-DEBUG: Sample 184: 0.016673
> > > PTB-DEBUG: Sample 185: 0.016657
> > > PTB-DEBUG: Sample 186: 0.016662
> > > PTB-DEBUG: Sample 187: 0.016665
> > > PTB-DEBUG: Sample 188: 0.016670
> > > PTB-DEBUG: Sample 189: 0.016667
> > > PTB-DEBUG: Sample 190: 0.016649
> > > PTB-DEBUG: Sample 191: 0.016662
> > > PTB-DEBUG: Sample 192: 0.016663
> > > PTB-DEBUG: Sample 193: 0.016676
> > > PTB-DEBUG: Sample 194: 0.016668
> > > PTB-DEBUG: Sample 195: 0.016651
> > > PTB-DEBUG: Sample 196: 0.016653
> > > PTB-DEBUG: Sample 197: 0.016666
> > > PTB-DEBUG: Sample 198: 0.016658
> > > PTB-DEBUG: Sample 199: 0.016671
> > > PTB-DEBUG: Sample 200: 0.016668
> > > PTB-DEBUG: Sample 201: 0.016652
> > > PTB-DEBUG: Sample 202: 0.016662
> > > PTB-DEBUG: Sample 203: 0.016688
> > > PTB-DEBUG: Sample 204: 0.016640
> > > PTB-DEBUG: Sample 205: 0.016660
> > > PTB-DEBUG: Sample 206: 0.016664
> > > PTB-DEBUG: Sample 207: 0.016666
> > > PTB-DEBUG: Sample 208: 0.016658
> > > PTB-DEBUG: Sample 209: 0.016665
> > > PTB-DEBUG: Sample 210: 0.016666
> > > PTB-DEBUG: Sample 211: 0.016657
> > > PTB-DEBUG: Sample 212: 0.016666
> > > PTB-DEBUG: Sample 213: 0.016665
> > > PTB-DEBUG: Sample 214: 0.016659
> > > PTB-DEBUG: Sample 215: 0.016660
> > > PTB-DEBUG: Sample 216: 0.016662
> > > PTB-DEBUG: Sample 217: 0.016663
> > > PTB-DEBUG: Sample 218: 0.016693
> > > PTB-DEBUG: Sample 219: 0.016637
> > > PTB-DEBUG: Sample 220: 0.016678
> > > PTB-DEBUG: Sample 221: 0.016646
> > > PTB-DEBUG: Sample 222: 0.016688
> > > PTB-DEBUG: Sample 223: 0.016641
> > > PTB-DEBUG: Sample 224: 0.016661
> > > PTB-DEBUG: Sample 225: 0.016664
> > > PTB-DEBUG: Sample 226: 0.016656
> > > PTB-DEBUG: Sample 227: 0.016681
> > > PTB-DEBUG: Sample 228: 0.016650
> > > PTB-DEBUG: Sample 229: 0.016674
> > > PTB-DEBUG: Sample 230: 0.016695
> > > PTB-DEBUG: Sample 231: 0.016619
> > > PTB-DEBUG: Sample 232: 0.016682
> > > PTB-DEBUG: Sample 233: 0.016648
> > > PTB-DEBUG: Sample 234: 0.016659
> > > PTB-DEBUG: Sample 235: 0.016662
> > > PTB-DEBUG: Sample 236: 0.016658
> > > PTB-DEBUG: Sample 237: 0.016670
> > > PTB-DEBUG: Sample 238: 0.016655
> > > PTB-DEBUG: Sample 239: 0.016672
> > > PTB-DEBUG: Sample 240: 0.016659
> > > PTB-DEBUG: Sample 241: 0.016655
> > > PTB-DEBUG: Sample 242: 0.016771
> > > PTB-DEBUG: Sample 243: 0.016563
> > > PTB-DEBUG: Sample 244: 0.016682
> > > PTB-DEBUG: Sample 245: 0.016642
> > > PTB-DEBUG: Sample 246: 0.016687
> > > PTB-DEBUG: Sample 247: 0.016636
> > > PTB-DEBUG: Sample 248: 0.016668
> > > PTB-DEBUG: Sample 249: 0.016660
> > > PTB-DEBUG: Sample 250: 0.016667
> > > PTB-DEBUG: Sample 251: 0.016654
> > > PTB-DEBUG: Sample 252: 0.016667
> > > PTB-DEBUG: Sample 253: 0.016679
> > > PTB-DEBUG: Sample 254: 0.016644
> > > PTB-DEBUG: Sample 255: 0.016662
> > > PTB-DEBUG: Sample 256: 0.016657
> > > PTB-DEBUG: Sample 257: 0.016666
> > > PTB-DEBUG: Sample 258: 0.016660
> > > PTB-DEBUG: Sample 259: 0.016673
> > > PTB-DEBUG: Sample 260: 0.016661
> > > PTB-DEBUG: Sample 261: 0.016685
> > > PTB-DEBUG: Sample 262: 0.016638
> > > PTB-DEBUG: Sample 263: 0.016685
> > > PTB-DEBUG: Sample 264: 0.016641
> > > PTB-DEBUG: Sample 265: 0.016661
> > > PTB-DEBUG: Sample 266: 0.016665
> > > PTB-DEBUG: Sample 267: 0.016660
> > > PTB-DEBUG: Sample 268: 0.016662
> > > PTB-DEBUG: Sample 269: 0.016662
> > > PTB-DEBUG: Sample 270: 0.016664
> > > PTB-DEBUG: Sample 271: 0.016656
> > > PTB-DEBUG: Sample 272: 0.016666
> > > PTB-DEBUG: Sample 273: 0.016668
> > > PTB-DEBUG: Sample 274: 0.016660
> > > PTB-DEBUG: Sample 275: 0.016676
> > > PTB-DEBUG: Sample 276: 0.016653
> > > PTB-DEBUG: Sample 277: 0.016660
> > > PTB-DEBUG: Sample 278: 0.016669
> > > PTB-DEBUG: Sample 279: 0.016661
> > > PTB-DEBUG: Sample 280: 0.016655
> > > PTB-DEBUG: Sample 281: 0.016676
> > > PTB-DEBUG: Sample 282: 0.016679
> > > PTB-DEBUG: Sample 283: 0.016633
> > > PTB-DEBUG: Sample 284: 0.016664
> > > PTB-DEBUG: Sample 285: 0.016674
> > > PTB-DEBUG: Sample 286: 0.016647
> > > PTB-DEBUG: Sample 287: 0.016666
> > > PTB-DEBUG: Sample 288: 0.016660
> > > PTB-DEBUG: Sample 289: 0.016669
> > > PTB-DEBUG: Sample 290: 0.016678
> > > PTB-DEBUG: Sample 291: 0.016649
> > > PTB-DEBUG: Sample 292: 0.016664
> > > PTB-DEBUG: Sample 293: 0.016663
> > > PTB-DEBUG: Sample 294: 0.016661
> > > PTB-DEBUG: Sample 295: 0.016664
> > > PTB-DEBUG: Sample 296: 0.016660
> > > PTB-DEBUG: Sample 297: 0.016661
> > > PTB-DEBUG: Sample 298: 0.016666
> > > PTB-DEBUG: Sample 299: 0.016664
> > > PTB-DEBUG: End of calibration data for this run...
> > > Saving minidump to file
> > > C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\matlab_crash_dump.3696.0.dmp
> > > ----------------------------------------------------------
> > -----
> > > Segmentation violation detected at Thu Mar 20 16:49:00 2008
> > > ----------------------------------------------------------
> > -----
> > > Configuration:
> > > MATLAB Version: 7.5.0.342 (R2007b)
> > > MATLAB License: 303224
> > > Operating System: Microsoft Windows XP
> > > Window System: Version 5.1 (Build 2600: Service Pack 2)
> > > Processor ID: x86 Family 15 Model 12 Stepping 2, AuthenticAMD
> > > Virtual Machine: Java 1.6.0 with Sun Microsystems Inc. Java
> > > HotSpot(TM) Client VM mixed mode
> > > Default Charset: windows-1252
> > > Register State:
> > > EAX = 00000000 EBX = 78144e50
> > > ECX = 139df930 EDX = 00076e49
> > > ESI = 00000000 EDI = 00000000
> > > EBP = 00cecce8 ESP = 00cecc3c
> > > EIP = 78144e6e FLG = 00010202
> > > Stack Trace:
> > > [0] MSVCR80.dll:0x78144e6e(0x00cecd20, 0x00ceced0, 2, 0)
> > > [1] Screen.dll:0x139b8c7a(0x00ced7fc, 2464, 257, 0)
> > > [2] Screen.dll:0x139a74d2(2, 0x00ced7fc, 9, 0x00ced88c)
> > > [3] libmex.dll:_mexRunMexFile(2, 0x00ced7fc, 9, 0x00ced88c) + 139 bytes
> > > [4] libmex.dll:private: void __thiscall
> > > Mfh_mex::runMexFileWithSignalProtection(int,struct mxArray_tag *
> > > *,int,struct mxArray_tag * *)(2, 0x00ced7fc, 9, 0x00ced88c) + 86 bytes
> > > [5] libmex.dll:public: virtual void __thiscall
> > > Mfh_mex::dispatch_file(int,struct mxArray_tag * *,int,struct
> > mxArray_tag
> > > * *)(2, 0x00ced7fc, 9, 0x00ced88c) + 261 bytes
> > > [6] m_dispatcher.dll:public: virtual void __thiscall
> > > Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag
> > > * *)(2, 0x00ced7fc, 9, 0x00ced88c) + 203 bytes
> > > [7] m_interpreter.dll:void __cdecl mdCallFunction(int,struct
> > > mxArray_tag * *,int,struct mxArray_tag * *,class Mfh_MATLAB_fn *)(2,
> > > 0x00ced7fc, 9, 0x00ced88c) + 56 bytes
> > > [8] m_interpreter.dll:public: void __thiscall
> > > ResolverFunctionDesc::CallFunction(int,struct mxArray_tag * *
> > > const,int,struct mxArray_tag * * const)(2, 0x00ced7fc, 9, 0x00ced88c) +
> > > 93 bytes
> > > [9] m_interpreter.dll:public: bool __thiscall
> > > Resolver::CallMFunction(int,int,class _m_operand * const,union
> > > m_operand_storage *,int,class _m_operand * const,union
> > m_operand_storage
> > > *,int *)(2, 2, 0x01569fa0, 0) + 1388 bytes
> > > [10] m_interpreter.dll:bool __cdecl inResolveMFunctionCall(struct
> > > _m_function_desc *,int,int,class _m_operand * const,union
> > > m_operand_storage *,int,class _m_operand * const,union
> > m_operand_storage
> > > *,int *,enum inMarshalType *,int,class mpsTypeSequenceNlhs const
> > > *,struct mxArray_tag * (__cdecl*)(int))(0x126b6638, 2, 2, 0x01569fa0) +
> > > 195 bytes
> > > [11] m_interpreter.dll:private: bool __thiscall
> > > accelImpl::MFunctionCall(struct _accelOp * *)(0x00cede98, 0xee6c3d7c,
> > > 0x03825ea0, 0x5cc05610) + 179 bytes
> > > [12] m_interpreter.dll:public: enum jitReturnFlags __thiscall
> > > accelImpl::Exec(void)(0xee6c3de4, 0x03825ea0, 1, 0x00cee24c) + 205 bytes
> > > [13] m_interpreter.dll:public: enum jitReturnFlags __thiscall
> > > accelCode::Call(enum inMarshalType *,int *)const (0x00cedf9c,
> > > 0x00cedf74, 0xee6c3ca8, 0) + 128 bytes
> > > [14] m_interpreter.dll:public: static bool __cdecl
> > > inJit::ExecuteHotSegment(struct _inJitAccelInfo *,enum opcodes *,int
> > > *,int *)(0x00cee044, 0x00cee0f8, 0x00cee0a8, 0x00cee24c) + 1898 bytes
> > > [15] m_interpreter.dll:int __cdecl inInterp(enum
> > > inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *,int
> > > *)(1, 0, 3, 0) + 338 bytes
> > > [16] m_interpreter.dll:int __cdecl protected_inInterp(enum
> > > inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(1, 0,
> > > 1, 0) + 87 bytes
> > > [17] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum
> > > inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(1, 0,
> > > 1, 0) + 274 bytes
> > > [18] m_interpreter.dll:int __cdecl inExecuteMFunctionOrScript(class
> > > Mfh_mp *,bool)(0x03876220 "D#ùy÷A", 0x03832201, 0xee6c0710, 0xffffffff)
> > > + 916 bytes
> > > [19] m_interpreter.dll:void __cdecl inRunMfile(int,struct mxArray_tag
> > > * *,int,struct mxArray_tag * *,class Mfh_mp *,struct inWorkSpace_tag
> > > *)(0, 0x00cee4c4, 0, 0x00cee524) + 673 bytes
> > > [20] m_interpreter.dll:public: virtual void __thiscall
> > > Mfh_mp::dispatch_file(struct _mdUnknown_workspace *,int,struct
> > > mxArray_tag * *,int,struct mxArray_tag * *)(0, 0, 0x00cee4c4, 0) +
> > 29 bytes
> > > [21] m_interpreter.dll:public: virtual void __thiscall
> > > Mfh_mp::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag
> > > * *)(0, 0x00cee4c4, 0, 0x00cee524) + 28 bytes
> > > [22] m_dispatcher.dll:public: virtual void __thiscall
> > > Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag
> > > * *)(0, 0x00cee4c4, 0, 0x00cee524) + 203 bytes
> > > [23]
> > > m_interpreter.dll:__catch$?inDispatchFromStack@@YAHHPBDHH@Z$0(602,
> > > 0x01580304 "TestOpenGL2", 0, 0) + 744 bytes
> > > [24] m_interpreter.dll:enum opcodes __cdecl inDispatchCall(char const
> > > *,int,int,int,int *,int *)(0x01580304 "TestOpenGL2", 602, 0, 0) +
> > 156 bytes
> > > [25] m_interpreter.dll:int __cdecl inInterp(enum
> > > inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *,int
> > > *)(2, 0, 0, 0) + 2739 bytes
> > > [26] m_interpreter.dll:int __cdecl protected_inInterp(enum
> > > inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(2, 0,
> > > 0, 0) + 87 bytes
> > > [27] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum
> > > inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *,int *)(2, 0,
> > > 0, 0) + 274 bytes
> > > [28] m_interpreter.dll:_inInterPcode(2, 0xee6c0be8, 0, 0x038c8820
> > > "TestOpenGL2\n") + 162 bytes
> > > [29] m_interpreter.dll:enum inExecutionStatus __cdecl
> > > in_local_call_eval_function(int *,struct _pcodeheader *,int *,struct
> > > mxArray_tag * * const,enum inDebugCheck,bool)(0x00cef2bc, 0x00cef32c,
> > > 0x00cef358, 2) + 152 bytes
> > > [30] m_interpreter.dll:enum inExecutionStatus __cdecl
> > > inEvalStringWithIsVarFcn(struct _memory_context *,char const *,enum
> > > EvalType,int,struct mxArray_tag * * const,enum inDebugCheck,struct
> > > _pcodeheader *,int *,bool (__cdecl*)(void *,char const *),void
> > > *,bool)(0x7ac2177c, 0x038c8820 "TestOpenGL2\n", 0, 0) + 2454 bytes
> > > [31] m_interpreter.dll:enum inExecutionStatus __cdecl
> > > inEvalCmdWithLocalReturnandtype(char const *,int *,enum
> > > inDebugCheck,bool)(0x038c8820 "TestOpenGL2\n", 0, 2, 0) + 107 bytes
> > > [32] m_interpreter.dll:_inEvalCmdNoEnd(0x038c8820 "TestOpenGL2\n", 0,
> > > 0xee4b5dc0, 0x7ab9e7f0) + 20 bytes
> > > [33] bridge.dll:enum inExecutionStatus __cdecl ThrowSignal(char const
> > > *)(0x038c8820 "TestOpenGL2\n", 0xee4b5a8c, 0x01483fd0, 0x01483f70) + 77
> > > bytes
> > > [34] bridge.dll:__catch$_mnParser$0(0xee571969, 0x01483f70,
> > > 0x01483f70, 0) + 292 bytes
> > > [35] mcr.dll:public: void __thiscall
> > > mcrInstance::mnParser(void)(0xee571149, 0x004043f0, 336710, 0) + 62
> > bytes
> > > [36] MATLAB.exe:0x00401414(4194304, 0, 336710, 10)
> > > [37] MATLAB.exe:0x00401733(0, 0, 0x7ffdd000, 0x80543ffd)
> > > [38] kernel32.dll:0x7c816fd7(0x00401910, 0, 0x78746341, 32)
> > > This error was detected while a MEX-file was running. If the MEX-file
> > > is not an official MathWorks function, please examine its source code
> > > for errors. Please consult the External Interfaces Guide for information
> > > on debugging MEX-files.
> > > If it is an official MathWorks function, please
> > > follow these steps to report this problem to The MathWorks so we
> > > have the best chance of correcting it:
> > > The next time MATLAB is launched under typical usage, a dialog box will
> > > open to help you send the error log to The MathWorks. Alternatively, you
> > > can send an e-mail to segv@ with the following file attached:
> > > C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\matlab_crash_dump.3696
> > > If the problem is reproducible, please submit a Service Request via:
> > > http://www.mathworks.com/support/contact_us/ts/help_request_1.html
> > <http://www.mathworks.com/support/contact_us/ts/help_request_1.html>
> > > A technical support engineer might contact you with further information.
> > > Thank you for your help. Save your workspace and restart MATLAB.
> > >
> > >
> > >
> > > Mario Kleiner wrote:
> > > >
> > > > Ok, workaround included in current PTB beta. UpdatePsychtoolbox to
> > > > get the latest beta release. Then try two things:
> > > >
> > > > 1. Screen('Preference', 'Verbosity', 6);
> > > > Run OpenGL demo again, post the Matlab output. The debug output
> > > > should allow to narrow down the faulty driver command. Maybe
> > > > we can provide a more focused workaround in the future, based on
> > > > that information.
> > > >
> > > > 2. In the future, add a Screen('Preference', 'ConserveVRAM', 8); to
> > > > the top of your OpenGL scripts to disable context isolation.
> > > >
> > > > -mario
> > > >
> > > > --- In psychtoolbox@yahoogroups.com
> > <mailto:psychtoolbox%40yahoogroups.com>
> > > > <mailto:psychtoolbox%40yahoogroups.com>, "csabacziraki"
> > > > <csabacziraki@> wrote:
> > > > >
> > > > > Thanks a lot for your help!
> > > > >
> > > > > --- In psychtoolbox@yahoogroups.com
> > <mailto:psychtoolbox%40yahoogroups.com>
> > > > <mailto:psychtoolbox%40yahoogroups.com>, "Mario Kleiner"
> > > > > <mario.kleiner@> wrote:
> > > > > >
> > > > > > Jap. The problem is that ACER doesn't design their notebooks
> > > > > > in a compliant fashion so they need these customized drivers
> > > > > > and that they don't care too much about customer support,
> > > > > > otherwise they would at least provide half-yearly
> > > > > > updates of their drivers.
> > > > > >
> > > > > > So the best solution for ACERs bug would be to ask them to
> > > > > > provide a driver update. Your gfx-card will also be incapable
> > > > > > of supporting any of the new features of PTB although the
> > > > > > hardware can do it, just insufficient outdated drivers.
> > > > > >
> > > > > > And its probably a good idea for Windows users to check the
> > > > > > webpages of graphcis vendors like ATI or NVidia before they
> > > > > > buy a portable and prefer a vendor that allows use of the
> > > > > > generic drivers - that way at least you get timely driver
> > > > > > updates.
> > > > > >
> > > > > > The next beta release will contain a switch to disable context
> > > > > > isolation for such broken systems. Then PTB will work with
> > > > > > OpenGL, but without the additional protection layer: Much
> > > > > > more time spent for you to hunt down bugs in your own
> > > > > > OpenGL code or finding unwanted interactions with PTB, not
> > > > > > fun at all. I already spent a workday on hunting such ghosts
> > > > > > in my own experiment code -- and i'm at a big advantage
> > > > > > knowing how everything works, so good luck for you if you
> > > > > > hit such a problem.
> > > > > >
> > > > > > -mario
> > > > >
> > > >
> > > >
> > >
> >
> >
>
>
> --
> Dr Jenny Read Office: +44 191 222 7559
> Royal Society University Research Fellow Mobile: +44 794 401 5796
> Institute of Neuroscience, Fax: +44 191 222 5622
> Newcastle University, Framlington Place, mailto:J.C.A.Read@...
> Newcastle upon Tyne, NE2 4HH, UK. http://www.staff.ncl.ac.uk/j.c.a.read
>