Odyssey : Is it possible to deactivate internal MediaPlayer ?

Hi,
Using Odyssey 1.23, I have often crash of "[OWB] MediaPlayer" when opening webpages with autoplayed videos.

As SMTube & WebReplay are enough for my videos needs, is it possible to deactivate OWB Mediaplayer ?


For example, on this page, even by deactivating video MIMETYPE, OWB Mediaplayer loads the video and crashs

http://www.jeuxvideo.com/videos/gamin ... action-sauce-samourai.htm





=>

Crash log for task "[OWB] MediaPlayer"
Generated by GrimReaper 53.19
Crash occured in module kernel at address 0x0200D1C8
Type of crash: DSI (Data Storage Interrupt) exception
Alert number: 0x80000003
...
    _ZN7WebCore18MediaPlayerPrivate10playerLoopEv()+0x4b0 (section 1 @ 0x1876E4)
    _ZN7WebCore18MediaPlayerPrivate15playerLoopStartEPv()+0x2c (section 1 @ 0x187FD4)
    _ZN3WTFL16threadEntryPointEPv()+0x130 (section 1 @ 0x17CE26C)



Thank you for your help.
Guillaume

@zzd10h

Mmm no it's not possible i think ..

Out of interest, is there anyone actively working on OWB for AOS4?

Thank you Samir,
I hoped that it was possible...

@ddni@samo79@all
do you encounter the same kind of problems ?

@zzd10h

No i don't have this problem, sure sometimes it can crash but generally (even if slow) all works as expected

As interim solution you might switch to the old 1.16, there is no video support on it and at the same time the 1.16 still pretty usable for any "normal" browsing

http://kas1e.mikendezign.com/aos4/odyssey/

@zzd10h

I get exactly the same crash as you.

Crash log for task "[OWB] MediaPlayer"
Generated by GrimReaper 53.19
Crash occured in module kernel at address 0x0200D1C8
Type of crash: DSI (Data Storage Interrupt) exception
Alert number:

Stack trace:
native kernel module kernel+0x0000d1c8
native kernel module newlib.library.kmod+0x00007e70
file_read()+0x2c (section 1 @ 0xD87980)
ffurl_read()+0xe8 (section 1 @ 0x1A8880C)
fill_buffer()+0xe0 (section 1 @ 0x1AB5FEC)
avio_rb32()+0xac (section 1 @ 0x1AB7B90)
mov_read_default()+0x12c (section 1 @ 0x1A93778)
mov_read_header()+0xc0 (section 1 @ 0x1A9A3AC)
avformat_open_input()+0x1dc (section 1 @ 0x1AB467C)
ac_open()+0xa4 (section 1 @ 0xD89548)
_ZN7WebCore18MediaPlayerPrivate10playerLoopEv()+0x4b0 (section 1 @ 0x1876E4)
_ZN7WebCore18MediaPlayerPrivate15playerLoopStartEPv()+0x2c (section 1 @ 0x187FD4)
_ZN3WTFL16threadEntryPointEPv()+0x130 (section 1 @ 0x17CE26C)
native kernel module dos.library.kmod+0x00024c18
native kernel module kernel+0x00042654
native kernel module kernel+0x000426d4

Mediaplayer of Odyssey is buggy, sometime i get a crash too.
I wish me that the new MPlayer would be the Mediaplayer of Odyssey.

@tommysammy

It may be buggy, but I'd never had the type of crash seen above, until I tried to disable the built in player via mimetypes.

Activating all of the mimetypes again fixes the crash.

@ddni@TommySammy@Samo79

Thank you for your replies.

You can disable Javascript on specific sites, I think the players are usually loaded by it.

It is unfortunate that it should be so buggy. Even if the mediaplayer itself doesn't crash, the whole system gets unstable after it has been used and often results in a crash or freeze somewhere else in Odyssey, Workbench or anywhere.

It's quite clear that it overwrites memory somewhere, maybe stack overflow?

@Deniil

When you are streaming somethings in OWB, for example a YouTube's video but even if you are streaming a simple web-radio you will see that at some point the internal player slowly consumes all the availible phisical memory of your Amiga, when it reach the "low limit" the whole browser lead to crash or just freeze

See this ticket: http://bugs.os4depot.net/?function=viewissue&issueid=893

@samo79

Yeah, like all of webkit it never frees any memory because it was written for systems with (working) swap. But Odyssey and the player gets unstable around when I have 700MB free ram. I never let Odyssey get below 700MB free (about 700MB allocated), preferable not below 1GB free, because it will surely crash very soon or lock up the system.

But I don't think running out of memory the biggest problem of the player. It trashes memory. If it has been started just once on any small video, the system is unstable and will crash after a while in some unexpected way that never happens when that player has not been run.