[mythtv] [mythtv-commits] Ticket #8512: Mythwelcome spawned frontend crashes when using internal web browser

[Mike Parker]

> -----Original Message-----
> From: mythtv-dev-bounces [at] mythtv
> [mailto:mythtv-dev-bounces [at] mythtv] On Behalf Of Michael T. Dean
> Sent: Tuesday, June 01, 2010 12:08 AM
> To: mythtv-dev [at] mythtv
> Subject: Re: [mythtv] [mythtv-commits] Ticket #8512:
> Mythwelcome spawned frontend crashes when using internal web browser
>
> On 05/31/2010 04:33 AM, MythTV wrote:
> > #8512: Mythwelcome spawned frontend crashes when using
> internal web browser
> >
> -------------------------------------------------+------------
> --------------
> > Reporter: Mike Parker<michael.parker@…> |
> Owner: paulh
> > Type: defect |
> Status: infoneeded_new
> > Priority: minor | Milestone:
> > Component: Plugin - MythBrowser |
> Version: 0.23-fixes
> > Severity: medium | Mlocked: 0
> >
> -------------------------------------------------+------------
> --------------
> >
> > Comment(by Mike Parker<michael.parker@…>):
> >
> > Backtrace attached, obtained after attaching gdb to the
> mythwelcome-
> > invoked mythfrontend. I attempted to follow the Wiki
> instructions but,
> > having found apport to be unavailable for Fedora 12,
> installed the ATRPMS
> > mythtv-debuginfo package and attached gdb manually.
> >
> > I'm in uncharted territory here, so please let me know if
> the backtrace is
> > insufficient etc.
> >
>
> Mike,
>
> Can you do me a favor and disable the IcedTeaPlugin (at least
> temporarily) and see if the crash still happens? We've had
> other people
> report issues with using MythBrowser with the IcedTeaPlugin, and it
> seems to be causing problems for you, too.
>
> If you don't get crashes without IcedTeaPlugin, it would be
> great if you
> could also test with the Oracle JDK plugin instead of the
> IcedTeaPlugin.
>
> Otto K (since you mention on IRC having crashes that seemed to be
> related to IcedTeaPlugin), were you using mythwelcome, too? Have you
> seen any more crashes since switching to the Sun^H^H^HOracle
> JDK plugin?
>
> Thanks,
> Mike
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
> Mike
>
> OK - I'll give it a go and report back - things have been conspiring against MythBox tinkering of late :o(
>
> Any idea why this issue only affects MythBrowser running in a frontend spawned by MythWelcome? I have no problems with MythBrowser when the 
> frontend is started "conventionally". How does MythWelcome invoke the frontend - anything unusual?
> 
> Cheers,
>
> Mike 

Mike,

I can confirm that removing the OpenJDK plugin resolves (or works around) the issue - webpages load successfully in both a MythBrowser session from a standalone frontend and from a frontend spawned by MythWelcome.

Having replaced OpenJDK with the Sun/Oracle JRE, I no longer have a problem.

However, I can't help but think this is a workaround for a genuine MythWelcome/MythFrontend/MythBrowser issue. There are definite differences in the two MythBrowser sessions - for instance, the loaded URL is displayed in the "progress bar" at the foot of the screen in a "standalone" MythBrowser session whilst it's not in a spawned browser session. I suspect that differing behaviour wrt. the OpenJDK plugin is another such difference.

*Something* is causing the two frontends (standalone and spawned) to differ when, AFAIK, they should be identical invocations of /usr/bin/mythfrontend (or similar). It's probably beyond my somewhat megre knowledge to determine what this difference is, but I'm more than willing to help someone who can.

Thanks for the OpenJDK pointer,

Mike