[mythtv-commits] Ticket #9447: MacOS X - Qt binaries log spam
MythTV
noreply at mythtv.org
Thu Jan 6 03:58:20 UTC 2011
#9447: MacOS X - Qt binaries log spam
-------------------------------------------------+-------------------------
Reporter: Craig Treleaven <ctreleaven@…> | Owner: nigel
Type: Bug Report | Status:
Priority: minor | accepted
Component: Ports - OSX | Milestone: unknown
Severity: medium | Version:
Keywords: | 0.24-fixes
| Resolution:
| Ticket locked: 0
-------------------------------------------------+-------------------------
Changes (by nigel):
* status: new => accepted
Old description:
> MythFrontend writes hundreds of log entries per second complaining about
> 2 sets of Qt binaries. Sample below; attached file has log from starting
> the frontend and immediately exiting--2,300 line.
>
> The main frontend functions seem to work properly (set up recording, play
> recording, etc) but the log spam makes it difficult to identify other
> problems.
>
> {{
> On Mac OS X, you might be loading two sets of Qt binaries into the same
> process. Check that all plugins are compiled against the right Qt
> binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of
> binaries are being loaded.
> QObject::moveToThread: Current thread (0x884a70) is not the object's
> thread (0x80a680).
> Cannot move to target thread (0x80a680)
> }}
New description:
MythFrontend writes hundreds of log entries per second complaining about 2
sets of Qt binaries. Sample below; attached file has log from starting
the frontend and immediately exiting--2,300 line.
The main frontend functions seem to work properly (set up recording, play
recording, etc) but the log spam makes it difficult to identify other
problems.
{{{
On Mac OS X, you might be loading two sets of Qt binaries into the same
process. Check that all plugins are compiled against the right Qt
binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of
binaries are being loaded.
QObject::moveToThread: Current thread (0x884a70) is not the object's
thread (0x80a680).
Cannot move to target thread (0x80a680)
}}}
--
Comment:
Can't reproduce with a fresh build on 10.6.5, but last time I encountered
that, moving the built libraries out of the way silenced the errors.
''i.e.'':
{{{
mv .osx-packager/build .osx-packager/build.old
}}}
I think it was caused by DYLD_LIBRARY_PATH containing the non-packaged
libraries, and the runtime system had two sets of identical libraries
being observed.
--
Ticket URL: <http://code.mythtv.org/trac/ticket/9447#comment:1>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list