{length = 6, capacity = 6, bytes = 0x0016cb8b9256}
MATLAB(1422,0xa000ed58) malloc: \*\*\* Deallocation of a pointer not malloced: 0xbfff83c0; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
??? Error using ==\> MacModelName
Wrong byte order in mapping file.
Error in ==\> DescribeComputer at 56
thisMacTytpe=MacModelName;
---
Russell A. Poldrack, Ph.d.
Associate Professor
UCLA Department of Psychology
Franz Hall, Box 951563
Los Angeles, CA 90095-1563
phone: 310-794-1224
fax: 310-206-5895
email: [poldrack@...](mailto:poldrack@...)
web: [www.poldracklab.org](http://www.poldracklab.org/)
---
### Author:  [@Allen\_Ingling](https://psychtoolbox.discourse.group/u/Allen_Ingling)
#### Post date: [May 27, 2006, 10:01pm UTC](https://psychtoolbox.discourse.group/t/ptb-on-intel/1624/2 "2006-05-27T22:01:21Z")
Hi Russ,
You might want to try running matlab from the terminal (ie Apple's
application). Before I made the mistake of installing the security update on
my MacBook Pro, I used matlab extensively in this manner for about a month
without any keyboard lock-ups.
In order to work well with X11 you will need to set the DISPLAY variable. To
do this I put the following code in my .cshrc script:
if (! $?DISPLAY) then
setenv DISPLAY :0.0
endif
Good luck,
-Aaron
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
Aaron Seitz, Ph.D.
Research Assistant Professor
Department of Psychology
Boston University
64 Cummington St.
Boston, MA 02215
Ph: (617) 353-1104
Fax: (617) 353-6933
Email: [aseitz@...](mailto:aseitz@...)
Web: [http://people.bu.edu/aseitz/](http://people.bu.edu/aseitz/)
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
> \> From: \<[psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com)\>
> \> Reply-To: \<[psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com)\>
> \> Date: 27 May 2006 19:17:36 -0000
> \> To: \<[psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com)\>
> \> Subject: [psychtoolbox] Digest Number 1342
> \>
> \> There is also a somewhat serious general problem using matlab under
> \> X11 on intel (which I've not been able to find on any of the
> \> discussion lists, though I've not dug incredibly deeply). When
> \> running MATLAB in an xterm or rxvt window under X11, it will
> \> regularly stop accepting keyboard input, such that one has to kill
> \> the window altogether. hopefully the upcoming matlab fix will deal
> \> with this issue.
> \>
---
### Author:  [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)
#### Post date: [May 29, 2006, 4:34pm UTC](https://psychtoolbox.discourse.group/t/ptb-on-intel/1624/3 "2006-05-29T16:34:32Z")
Hi Russ,
could you upgrade to the latest beta and retest? The warnings you've
seen are just warnings, not fatal errors. They tell you that
rasterbeam position queries don't work on your setup and that PTB is
using a less accurate fallback-path. I've improved the code in the
beta so that it differentiates between "beamposition queries not
supported by system" and "beamposition queries supported but not
working properly" on OS-X. In case of missing functionality, it now
silently switches to the fallback code instead of outputting a lot of
scary warnings - There's no point outputting warnings if one can't do
anything to fix them. The same fallback code is always silently used
on M$-Windows, as this system doesn't support beampos queries. In
practice it means that timing noise for reported stimulus onset
timestamps (the return value 'vbl' of vbl=Screen('Flip')) can increase
from reliably less than 100 microseconds on OS-X/PowerPC to something
in the order of multiple 100 microseconds up to occasional spikes of
multiple milliseconds. This only refers to the reported timestamps and
the internal timing checks. \*Stimulus onset\* will be still synced to
retrace with microsecond accuracy.
It would be sad if beamposition queries would get removed from the
gfx-drivers on Intel-Macs - a step back for OS-X and in the direction
of M$-Windows. But maybe this is just a temporal limitation and the
drivers will improve with future OS-X software updates.
I tried to "fix" MacModelName as well: It should shut up instead of
giving error messages. That's not a real fix, because Apple decided to
change the format of some name mapping files in OS-X 10.4.5 to break
this function. Would need to be rewritten from scratch to get it
working again :(
best,
-mario
--- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), Russell Poldrack \
wrote:
> \>
> \> I finally had a change to try out the PTB (using the current beta
> \> version) on my MacBook Pro running MATLAB 7.2. The short story is
> \> that it doesn't work. The longer story is that anything that calls
> \> screen seems to end with the flashing red caution screen. below is a
> \> printout of the output from one of these crashes, in case it's useful
> \> (I tried several of the various tests and they all failed with the
> \> same message).
> \>
> \> There is also a somewhat serious general problem using matlab under
> \> X11 on intel (which I've not been able to find on any of the
> \> discussion lists, though I've not dug incredibly deeply). When
> \> running MATLAB in an xterm or rxvt window under X11, it will
> \> regularly stop accepting keyboard input, such that one has to kill
> \> the window altogether. hopefully the upcoming matlab fix will deal
> \> with this issue.
> \>
> \> cheers,
> \> russ
> \>
> \> \>\> TestDrawingStuffOSX or TestTextureOSX
> \>
> \>
> \> PTB-INFO: This is the Screen-Prototype for PTB 1.0.7, intended as
> \> update for Psychtoolbox
> \> 1.0.6
> \> PTB-INFO: Implementation details may change in the final release for
> \> Psychtoolbox 1.0.7 -
> \> Use at your own Risk!
> \>
> \>
> \>
> \> OpenGL-Extensions are: GL\_ARB\_transpose\_matrix GL\_ARB\_vertex\_program
> \> GL\_ARB\_vertex\_blend G
> \> L\_ARB\_window\_pos GL\_ARB\_shader\_objects GL\_ARB\_vertex\_shader
> \> GL\_EXT\_multi\_draw\_arrays GL\_EX
> \> T\_clip\_volume\_hint GL\_EXT\_rescale\_normal GL\_EXT\_draw\_range\_elements
> \> GL\_EXT\_fog\_coord GL\_AP
> \> PLE\_client\_storage GL\_APPLE\_specular\_vector GL\_APPLE\_transform\_hint
> \> GL\_APPLE\_packed\_pixels
> \> GL\_APPLE\_fence GL\_APPLE\_vertex\_array\_object
> \> GL\_APPLE\_vertex\_program\_evaluators GL\_APPLE\_e
> \> lement\_array GL\_APPLE\_flush\_render GL\_NV\_texgen\_reflection
> \> GL\_NV\_light\_max\_exponent GL\_IBM
> \> \_rasterpos\_clip GL\_SGIS\_generate\_mipmap GL\_ARB\_shading\_language\_100
> \> GL\_ARB\_imaging GL\_ARB\_
> \> point\_parameters GL\_ARB\_texture\_env\_crossbar
> \> GL\_ARB\_texture\_border\_clamp GL\_ARB\_multitextu
> \> re GL\_ARB\_texture\_env\_add GL\_ARB\_texture\_cube\_map
> \> GL\_ARB\_texture\_env\_dot3 GL\_ARB\_multisamp
> \> le GL\_ARB\_texture\_env\_combine GL\_ARB\_texture\_compression
> \> GL\_ARB\_texture\_mirrored\_repeat GL
> \> \_ARB\_shadow GL\_ARB\_depth\_texture GL\_ARB\_shadow\_ambient
> \> GL\_ARB\_fragment\_program GL\_ARB\_frag
> \> ment\_shader GL\_ARB\_occlusion\_query GL\_ARB\_point\_sprite
> \> GL\_ARB\_vertex\_buffer\_object GL\_ARB\_
> \> pixel\_buffer\_object GL\_EXT\_compiled\_vertex\_array
> \> GL\_EXT\_framebuffer\_object GL\_EXT\_texture\_
> \> rectangle GL\_ARB\_texture\_rectangle GL\_EXT\_texture\_env\_add
> \> GL\_EXT\_blend\_color GL\_EXT\_blend\_
> \> minmax GL\_EXT\_blend\_subtract GL\_EXT\_texture\_lod\_bias GL\_EXT\_abgr
> \> GL\_EXT\_bgra GL\_EXT\_stenci
> \> l\_wrap GL\_EXT\_texture\_filter\_anisotropic
> \> GL\_EXT\_separate\_specular\_color GL\_EXT\_secondary\_c
> \> olor GL\_EXT\_blend\_func\_separate GL\_EXT\_shadow\_funcs
> \> GL\_EXT\_texture\_compression\_s3tc GL\_EXT
> \> \_texture\_compression\_dxt1 GL\_EXT\_blend\_equation\_separate
> \> GL\_EXT\_texture\_mirror\_clamp GL\_AP
> \> PLE\_ycbcr\_422 GL\_APPLE\_vertex\_array\_range GL\_APPLE\_texture\_range
> \> GL\_APPLE\_float\_pixels GL\_
> \> ATI\_texture\_float GL\_APPLE\_pixel\_buffer GL\_NV\_blend\_square
> \> GL\_NV\_fog\_distance GL\_ATI\_textu
> \> re\_mirror\_once GL\_ATI\_text\_fragment\_shader
> \> GL\_ATI\_blend\_equation\_separate GL\_ATI\_blend\_wei
> \> ghted\_minmax GL\_ATI\_texture\_env\_combine3 GL\_ATI\_separate\_stencil
> \> GL\_ATI\_texture\_compressio
> \> n\_3dc GL\_SGIS\_texture\_edge\_clamp GL\_SGIS\_texture\_lod GL\_SGI\_color\_matrix
> \>
> \>
> \> WARNING: Querying rasterbeam-position doesn't work on your setup!
> \> (Returns a constant valu
> \> e)
> \>
> \> WARNING: Couldn't determine end-line of vertical blanking interval
> \> for your display! Troub
> \> le with beamposition queries?!?
> \>
> \>
> \> PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: ATI Radeon
> \> X1600 OpenGL Engine :: 1.
> \> 5 ATI-1.4.26
> \> PTB-INFO: Renderer has 256 MB of VRAM and a maximum 250 MB of texture
> \> memory.
> \> PTB-Info: VBL startline = 900 , VBL Endline = -1
> \> PTB-Info: Measured monitor refresh interval from VBLsync = 16.699048
> \> ms [59.883654 Hz]. (5
> \> 0 valid samples taken, stddev=0.047322 ms.)
> \> PTB-Info: Small deviations between reported values are normal and no
> \> reason to worry.
> \> PTB-INFO: Using OpenGL GL\_TEXTURE\_RECTANGLE\_EXT extension for
> \> efficient high-performance t
> \> exture mapping...
> \>
> \> WARNING: Mismatch between measured monitor refresh intervals! This
> \> indicates problems with
> \> rasterbeam position queries.
> \>
> \>
> \> ----- ! PTB - WARNING: SYNCHRONIZATION TROUBLE ! ----
> \>
> \> One or more internal checks (see Warnings above) indicate that
> \> queries of rasterbeam position are not properly working for your setup.
> \>
> \> This will cause Screen('Flip') to report less accurate/robust timestamps
> \> (VBLTimestamp, StimulusOnsetTime) for stimulus timing. As accurate
> \> timestamps are crucial
> \> for
> \> properly timed stimulus presentation and automatic checking of
> \> presentation timing, you ma
> \> y experience
> \> an excessive number of skipped frames / wrong presentation deadlines
> \> \*plus\* the built-in c
> \> heck for such
> \> problems doesn't work reliably anymore!
> \>
> \>
> \> Please try the following measures to solve or work-around the problem:
> \> 1. Make sure that your machine is not running other demanding
> \> software in parallel and the
> \> n retry.
> \> 2. If you use a dual-display setup, please put all displays in mirror-
> \> mode with same resol
> \> ution and color depth.
> \> 3. If it doesn't help or is not possible, try to change assignment of
> \> the primary- and sec
> \> ondary display.
> \> 4. On desktops or tower machines with two external display
> \> connectors, \*PHYSICALLY\* swap t
> \> he connections, aka
> \> which display is plugged into which video-out socket at the back-
> \> side of your computer.
> \> 5. If that doesn't help or is not possible on dual- or multi-display
> \> setup, disconnect or
> \> disable all displays except
> \> the one for stimulus presentation to the subject.
> \>
> \>
> \> If everything fails, please report your problem including all these
> \> messages and informati
> \> on on your specific
> \> setup (Type of graphics card and connected displays, output of
> \> 'DescribeComputer') to the
> \> Psychtoolbox forum.
> \> -\> You may have found a bug in MacOS-X or your graphics-hardware.
> \>
> \>
> \> (I also found that DescribeComputer doesn't work correctly, due to a
> \> problem with MacModelName):
> \>
> \> \>\> DescribeComputer
> \> \{length = 6, capacity = 6, bytes =
> \> 0x0016cb8b9256}
> \> MATLAB(1422,0xa000ed58) malloc: \*\*\* Deallocation of a pointer not
> \> malloced: 0xbfff8370; This could be a double free(), or free() called
> \> with the middle of an allocated block; Try setting environment
> \> variable MallocHelp to see tools to help debug
> \> \{length = 6, capacity = 6, bytes =
> \> 0x0016cb8b9256}
> \> MATLAB(1422,0xa000ed58) malloc: \*\*\* Deallocation of a pointer not
> \> malloced: 0xbfff83c0; This could be a double free(), or free() called
> \> with the middle of an allocated block; Try setting environment
> \> variable MallocHelp to see tools to help debug
> \> ??? Error using ==\> MacModelName
> \> Wrong byte order in mapping file.
> \>
> \> Error in ==\> DescribeComputer at 56
> \> thisMacTytpe=MacModelName;
> \>
> \>
> \>
> \>
> \>
> \> ---
> \> Russell A. Poldrack, Ph.d.
> \> Associate Professor
> \> UCLA Department of Psychology
> \> Franz Hall, Box 951563
> \> Los Angeles, CA 90095-1563
> \>
> \> phone: 310-794-1224
> \> fax: 310-206-5895
> \> email: poldrack@...
> \> web: www.poldracklab.org
> \>
---
### Author:  [@fzhou1999](https://psychtoolbox.discourse.group/u/fzhou1999)
#### Post date: [July 5, 2006, 10:15pm UTC](https://psychtoolbox.discourse.group/t/ptb-on-intel/1624/4 "2006-07-05T22:15:46Z")
Mario,
I commented the priority ( ) command, and it seems to be working without freezing now.
Thanks! I wonder why the priority command causes matlab to crash.
A side note, I had installed the stand alone update to 10.4.7, but it didn't help.
Thanks,
Feng
-----------
Feng Zhou, Ph.D.
Department of Psychological and Brain Sciences
Johns Hopkins University
Ames 139
3400 N. Charles St
Baltimore, MD 21218
Email: [fengzhou@...](mailto:fengzhou@...) webpage: [http://psy.jhu.edu/~fengzhou](http://psy.jhu.edu/~fengzhou)
Office phone: 410 516 4030 Cell phone: 617 319 6766
---
### Author:  [@fzhou1999](https://psychtoolbox.discourse.group/u/fzhou1999)
#### Post date: [July 6, 2006, 7:56pm UTC](https://psychtoolbox.discourse.group/t/ptb-on-intel/1624/5 "2006-07-06T19:56:16Z")
Mario,
Regarding freezing vs. crashing, they had both occurred. However, the good news is that my
program runs fine now, even with the Priority command. So it seems updating both PTB to
beta and installing the stand alone OS 10.4.7 update fixed the problem of Screen function
on Intel Mac.
PTB Beta also seems to have fixed some keyboard and mouse problems with my system. I can
fully run experiments in my Macbook Pro now.
Thanks again!
Feng