On Wed, Apr 23, 2014 at 02:54:39PM +0000, Karl Dahlke wrote:
> Yes the URL class is a royal pain.
> See jsrt line 537 for all the stuff it's suppose to do.
> Lots of side effects, lots of setters.

Yeah I've had a *brief* look at it and it looks crazy.

> If you find a reproducible pathway to make the assert happen
> I'll track through the code and look for something amiss.
> I don't have a debug version build, but the regular version from Redhat
> I can't get to fail, and I've tried running large blocks
> of my jsrt code in a loop 100,000 times over and it seems to work.
> So I guess I'm just not hitting the right combination.

No, it's just the asserts aren't present in the non-debug builds apparently.
The only way you'll see this is to build a debug build of mozjs (as recommended
for debugging and development on their website).
I suspect there's probably a bug somewhere which is being caught by the debug
build but hasn't (yet) manifested itself.
As for making the assert happen, it's simply a case of loading jsrt (or
seemingly anything) with js enabled on my build of mozjs.

> I have no changes pending, nothing in work.
> Chris is working on something but it's all over in sendmail.c land.
> So if you do have time and want to investigate, the *cpp files are quiescent.
> If other things are going on in your world I understand;
> maybe you can just make the assert happen and I'll take it from there.

I had a *quick* go at debugging this yesterday but I really don't have time to
go through the mozjs code to try and understand why we're breaking something now.
This is because I'm in the final year of my university course and have a couple
of assignments, one of which being an 8000 plus word report,
due in for next week. After that I've got final exams to revise for but I
*might* have a bit more time to do edbrowse related development after next 
Friday.

Cheers,
Adam.