Re: What are the issues with X11 in OS X Mavericks?
Re: What are the issues with X11 in OS X Mavericks?
- Subject: Re: What are the issues with X11 in OS X Mavericks?
- From: Will Mortensen <email@hidden>
- Date: Fri, 25 Oct 2013 00:09:42 -0700
I just launched Wireshark for the first time after installing Mavericks and reinstalling Xquartz 2.7.5-rc2. It indeed took a minute or so to launch, with wireshark-bin using ~100% CPU and displaying nothing. A spindump showed that essentially all of this time was in fontconfig, rebuilding the cache. Subsequent launches were nice and quick.
I don't see this as a major problem.
On Oct 24, 2013, at 8:03 PM, Jeremy Huddleston Sequoia <email@hidden> wrote:
>
> On Oct 24, 2013, at 15:52, Merton Campbell Crockett <email@hidden> wrote:
>
>>
>> On Oct 24, 2013, at 12:20 , Jeremy Huddleston Sequoia <email@hidden> wrote:
>>
>>>> On 24 Oct 2013, at 19:13, Merton Campbell Crockett wrote:
>>>>
>>>>> This morning I tried running Wireshark again. Instead of aborting Wireshark when it failed to start within a minute, I left it “running” and went on to other things. After about 5 minutes, the Wireshark splash screen appeared followed by its normal startup window. Since then, Wireshark starts much more quickly than it ever did under earlier OS X releases.
>>>>
>>>> The first time you run an X11 program that uses fontconfig, all fonts in the system are scanned and some kind of database or cache is created (and that can take several minutes). Maybe that's what happened?
>>>
>>> XQuartz's font cache is generated during the postinstall script phase (that's why it takes a long time with that install phase).
>>>
>>> But you're probably close to the issue. wireshark has its own version of fontconfig, and I thought it used to show a caching progress bar while it was generating the font caches (on first execution), but maybe it wasn't shown for some reason.
>>
>> There is a progress bar on Wireshark’s “splash screen” as it initializes that is followed by the Wireshark’s “start screen” where you select the interface that you want to monitor and configure any filters that you need. The issue that I saw was the extraordinarily long delay between the “sudo wireshark” and the “splash screen” being displayed the first time that it was executed.
>
> a) You should not be running it under sudo. There's no need for such privilege escalation.
>
> b) It would've been nice to see a spindump during that period as it would show what wireshark was doing.
>
>> After the first execution of Wireshark, Wireshark’s “splash screen” is displayed much more quickly than it did on any earlier release of OS X.
>>
>> What I surmise, and it is a supposition, is that Apple is constructing a compressed image of the application and writing it out to disk.
>
> No.
>
>> If your goal is to improve system performance by compressing inactive applications, your have to address the problem of swapping inactive applications to disk. For a “standard” OS X application, it would be easy to provide a compressed memory image of the application in the update distribution. Apple couldn’t do this for the X-window environment as X11 is no longer distributed with OS X.
>
> No. This is not the case.
>
>> A second part of the problem is: “Which X-windows applications should be pre-compressed and included in the distribution?” My interest in networking tools is unlikely to coincide with others interests.
>
> There is no compression going on anywhere here.
>
> The only thing that could tell us what was going on is a spindump.
>
> --Jeremy
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden