I think the EOC marker problems are usually associated with corrupt jpeg 2000 textures, though I think there may also be a bug on 64-bit that causes issues here.

I'm not sure why you're seeing ODE errors. I would predict that these would not go away when reverting to 0.7.2 but it would be something to at least try.

The file sharing issues when loading an OAR may be due to a weakness in the flotsam cache code which allows race conditions when cache writing is launched on its own delegate. This should not be fatal since at least one thread will have correctly cached the asset. However, it would be nice to have the failure details in a Mantis.

I think you've previously said that you have to have physical prims. However, if you want to narrow down the problem you could try flipping the physical_prim = false switch in [Startup] in OpenSim.ini and see if that does alleviate the problem.

On 18/04/12 20:53, Fleep Tuque wrote:
Hmm, I dunno, something else seems to be going on, after the OAR finished 
loading, I see:

Region (UCSIM Staff 1) # [WARNING]: EOC marker not found. Codestream is corrupte
d.
[WARNING]: EOC marker not found. Codestream is corrupted.
[WARNING]: EOC marker not found. Codestream is corrupted.
[WARNING]: EOC marker not found. Codestream is corrupted.
[WARNING]: EOC marker not found. Codestream is corrupted.
[WARNING]: EOC marker not found. Codestream is corrupted.
[WARNING]: EOC marker not found. Codestream is corrupted.
[WARNING]: EOC marker not found. Codestream is corrupted.

This on top of the ODE Scene errors that seem to persist whether physical prims 
are enabled or not, and whether I start
the process with opensim.exe or opensim.32bitlaunch.exe..  0.7.3. is feeling 
pretty glitchy at the moment.

I'm thinking of reverting to 0.7.2 at least on the campus grid, it seemed more 
stable.  The only thing stopping me is
the thought of having to re-re-fix all those chairs that will have to be 
re-re-re-fixed again when we upgrade.  ;)

- Chris/Fleep


Chris M. Collins (SL/OS: Fleep Tuque)
Center for Simulations & Virtual Environments Research (UCSIM)
UCIT Instructional & Research Computing
University of Cincinnati
406A Zimmer Hall
315 College Drive
PO BOX 210088
Cincinnati, OH 45221-0088
[email protected] <mailto:[email protected]>
(513) 556-3018

http://ucsim.uc.edu

On Wed, Apr 18, 2012 at 3:46 PM, Garmin Kawaguichi 
<[email protected]
<mailto:[email protected]>> wrote:

    __
    I found that kind of error when I worked these days on load/save oar;  Look 
at Mantis 0005970
    I suppose a (temp?) file created by load oar was not released and an other 
process tries to open it.
    If you found where exactly it was first used, try to add
    typeoffile.Dispose();
    GCI

        ----- Original Message -----
        *From:* Fleep Tuque <mailto:[email protected]>
        *Sent:* Wednesday, April 18, 2012 9:31 PM
        *Subject:* [Opensim-users] Flotsam asset cache error - process cannot 
access file because it is being used by
        another process

        Anyone know why I would be seeing errors like this when trying to 
upload an OAR file?

        15:30:25 - [FLOTSAM ASSET CACHE]: Failed to update cache for asset 
faecc7e2-60e1
        -e9a9-e974-927ad18e8b51.  Exception The process cannot access the file 
'c:\opens
        im7_0.7.3\bin\assetcache\fae\faecc7e2-60e1-e9a9-e974-927ad18e8b51' 
*because it is*
        * being used by another process.*    at 
System.IO.__Error.WinIOError(Int32 errorCo
        de, String maybeFullPath)


    _______________________________________________
    Opensim-users mailing list
    [email protected] <mailto:[email protected]>
    https://lists.berlios.de/mailman/listinfo/opensim-users




_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users


--
Justin Clark-Casey (justincc)
http://justincc.org/blog
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users

Reply via email to