No subject
Fri Jun 12 11:19:36 PDT 2009
open a file anymore. Could happen even before we even try any neywork
activity (UI bitmaps for instance not loading in the login screen). I'm
wondering if the updated libs used with the patch (see install.xml) could be
the cause of this...
Not great news I know but I wanted to give some update before the weekend.
Cheers,
- Merov
On Thu, Sep 24, 2009 at 6:05 PM, Philippe (Merov) Bossut <
merov at lindenlab.com> wrote:
> Hi guys,
>
> I'm asking for help again: Pixel Gausman found a problem with running on
> Windows XP SP2 if the path to SLPlugin.exe (the external plugin launcher)
> contains white space (see PJIRA for details). I cannot reproduced the
> problem on Windows XP SP3. Could someone else try to confirm the problem?
> Other flavor of Windows? Thanks...
>
> Also, though the code path is pretty different between Windows and
> Linux/Mac wrt to process launching, it's not a bad idea to test with various
> exotic path... (spaces, diacritic characters, non latin...).
>
> Cheers,
> - Merov
>
>
> On Wed, Sep 23, 2009 at 10:57 AM, Philippe (Merov) Bossut <
> merov at lindenlab.com> wrote:
>
>> Hi guys,
>>
>> So, there's this big monster of a patch I posted on PJIRA since a week
>> now. Thanks a millions to those who tested it and reported issues
>> (incorporating fixes now). In the meantime, I've been working on a "Hello
>> World" plugin example so that I can contribute to a first draft of a "How to
>> write a plugin" doc and get some of you guys to start hacking.
>>
>> I'm happy to report that I do have such a plugin working on my machine
>> (yeah!) and, of course, that got me some new ideas on how to improve things,
>> develop new plug ins, extend the plugin architecture, etc... all things I
>> can't do while the big patch hasn't been committed.
>>
>> Add to that that I need to svn update my local repo and tweak that patch
>> every time a commit is done on trunk and you'll understand why I'm eager to
>> see this landing.
>>
>> So, what else do we need to commit this? I heard that we need more tests
>> but it seems we don't get any significant amount of tests unless we land in
>> trunk and produce binaries... which really makes me think I should commit
>> this before Friday so we can make the 1.2 schedule Robla emailed earlier.
>> What do you guys think? Is there one think that we need to do before that
>> first commit?
>>
>> One last note : the bulk of this code has been tested and qualified
>> internally already so it's not completely untested code. That makes me a
>> little more confident with the process.
>>
>> Cheers,
>> - Merov
>>
>>
>
--001485f725789d20250474714b6c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi guys,<br><br>I've been banging my head all day on a vexing problem w=
ith this patch on Mac. Aimee and me reported the same issue on IRC but we b=
oth wrote it off on some silly install we did on our dev environment. Seeme=
d weird enough we'd get the same issue so digging deeper, it looks like=
the problem is more serious. I won't go into the gory details but here=
's the short version:<br>
- On Mac, you get to a point where no texture download at all, you basicall=
y walk in a land of gray...<br>- It's not systematic mind you (things d=
o sometimes work fine)<br>- When it starts though, it's there to stay<b=
r>
- the trunk version or plugin-api are not affected: so it's something I=
did when merging (haven't identified what yet...)<br>- Clearing the ca=
che doesn't work: actually, it's a way to get the problem to repro.=
It seems that the file texture.cache can't get created at all...<br>
- Launching an unaffected version of the viewer makes the problem go away f=
or a while... till it starts again...<br><br>From the logs and some trackin=
g, it seems that, at some point, we just can't open a file anymore. Cou=
ld happen even before we even try any neywork activity (UI bitmaps for inst=
ance not loading in the login screen). I'm wondering if the updated lib=
s used with the patch (see install.xml) could be the cause of this...<br>
<br>Not great news I know but I wanted to give some update before the weeke=
nd.<br><br>Cheers,<br>- Merov<br><br><div class=3D"gmail_quote">On Thu, Sep=
24, 2009 at 6:05 PM, Philippe (Merov) Bossut <span dir=3D"ltr"><<a href=
=3D"mailto:merov at lindenlab.com">merov at lindenlab.com</a>></span> wrote:<b=
r>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi guys,<br><br>I=
'm asking for help again: Pixel Gausman found a problem with running on=
Windows XP SP2 if the path to SLPlugin.exe (the external plugin launcher) =
contains white space (see PJIRA for details). I cannot reproduced the probl=
em on Windows XP SP3. Could someone else try to confirm the problem? Other =
flavor of Windows? Thanks...<br>
<br>Also, though the code path is pretty different between Windows and Linu=
x/Mac wrt to process launching, it's not a bad idea to test with variou=
s exotic path... (spaces, diacritic characters, non latin...).<br><br>
Cheers,<br><font color=3D"#888888">
- Merov</font><div><div></div><div class=3D"h5"><br><br><div class=3D"gmail=
_quote">On Wed, Sep 23, 2009 at 10:57 AM, Philippe (Merov) Bossut <span dir=
=3D"ltr"><<a href=3D"mailto:merov at lindenlab.com" target=3D"_blank">merov=
@lindenlab.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi guys,<br><br>So, there's this big monster of a patch I posted on PJI=
RA since a week now. Thanks a millions to those who tested it and reported =
issues (incorporating fixes now). In the meantime, I've been working on=
a "Hello World" plugin example so that I can contribute to a fir=
st draft of a "How to write a plugin" doc and get some of you guy=
s to start hacking. <br>
<br>I'm happy to report that I do have such a plugin working on my mach=
ine (yeah!) and, of course, that got me some new ideas on how to improve th=
ings, develop new plug ins, extend the plugin architecture, etc... all thin=
gs I can't do while the big patch hasn't been committed. <br>
<br>Add to that that I need to svn update my local repo and tweak that patc=
h every time a commit is done on trunk and you'll understand why I'=
m eager to see this landing.<br><br>So, what else do we need to commit this=
? I heard that we need more tests but it seems we don't get any signifi=
cant amount of tests unless we land in trunk and produce binaries... which =
really makes me think I should commit this before Friday so we can make the=
1.2 schedule Robla emailed earlier. What do you guys think? Is there one t=
hink that we need to do before that first commit?<br>
<br>One last note : the bulk of this code has been tested and qualified int=
ernally already so it's not completely untested code. That makes me a l=
ittle more confident with the process.<br><br>Cheers,<br><font color=3D"#88=
8888">- Merov<br>
<br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>
--001485f725789d20250474714b6c--
More information about the SLDev
mailing list