[Bug 615357] [macosx] Handle multi-arch plugin-scanner

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=615357
  GStreamer | gstreamer (core) | git

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|0.10.34                     |0.10.33

--- Comment #25 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2011-04-11 10:42:51 UTC ---
Ok, committed this for now with cosmetic changes:

 commit 159cf687a1b63f334ecec5e0b1ea4cd1bc8e7537
 Author: Jan Schmidt <thaytan at mad.scientist.com>
 Date:   Mon Apr 11 11:29:00 2011 +0100

    pluginloader: make sure gst-plugin-scanner is called with the right arch on
OSX

    On OSX, GStreamer might be built as a 'fat/universal' binary containing
    both 32-bit and 64-bit code. We must take care that gst-plugin-scanner
    is executed with the same architecture as the GStreamer core, otherwise
    bad things may happen and core/scanner will not be able to communicate
    properly.

    Should fix issues with (32-bit) firefox using a 32-bit GStreamer core
    which then spawns a 'universal' gst-plugin-scanner binary which gets
    run in 64-bit mode, causing 100% cpu usage / busy loops or just hanging
    firefox until killed.

    https://bugzilla.gnome.org/show_bug.cgi?id=615357

Would be great if someone could confirm that it actually fixes the issue for
them.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.