# Fail Testing Mosek 8 -\> ERROR: LoadError: ReadOnlyMemoryError()

**URL:** <https://discourse.julialang.org/t/fail-testing-mosek-8-error-loaderror-readonlymemoryerror/8891>\
**Category:** Optimization (Mathematical)\
**Tags:** mosek\
**Created:** [February 7, 2018, 11:55am UTC](https://discourse.julialang.org/t/fail-testing-mosek-8-error-loaderror-readonlymemoryerror/8891 "2018-02-07T11:55:48Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![y4lu](https://avatars.discourse-cdn.com/v4/letter/y/47e85d/32.png) [@y4lu](https://discourse.julialang.org/u/y4lu)\
**Post date:** [February 9, 2018, 5:03am UTC](https://discourse.julialang.org/t/fail-testing-mosek-8-error-loaderror-readonlymemoryerror/8891/6 "2018-02-09T05:03:31Z")

</div>

I’ve had that error once or twice when using readcsv / readdlm on kaggle’s kernels platform, passing though an IOBuffer with default settings (readable=true / writeable = true / etc) seemed to help. [/readonly? fix for readdlm](https://discourse.julialang.org/t/csv-jls-csv-write-seems-slow/7643/12)  
Reading a file probably shouldn’t need write access though.

-Added: had a little dig and there’s a `fill( **readonly?** stringbuff, 1,0 ) ` hiding in DLMStore() -base/dataFmt.jl line 211 that might err if it passes a reference?

---

_[View the full topic](https://discourse.julialang.org/t/fail-testing-mosek-8-error-loaderror-readonlymemoryerror/8891)._