Subj : Re: Narrowed the problem down to...and solved To : netscape.public.mozilla.jseng From : "Sterling Bates" Date : Sat Nov 08 2003 07:02 pm "Brendan Eich" wrote in message news:3FAC880C.3020005@meer.net... > Sterling Bates wrote: > > >In one instance I was using a JS_NewString(...) to create a JSString, but > >the problem went away when I changed that to JS_NewStringCopyZ. > > What was arbitrary in that? If you passed off ownership of string > memory via JS_NewString but then reneged by freeing the storage > yourself, the memory would be double-freed. A breakpoint is one of the > kinder responses to that ;-). I did notice that msvcr70 is very polite :-) Actually the only code that changed was from _NewString to _NewStringCopyZ. I didn't explicitly manage anything on my end. FWIW, I had seen this several months ago, but didn't really pay attention to what was happening. To balance what I'm saying, however, I do have enough experience to know that things don't "just happen," so I'll eventually figure it out. > Is anyone using your bridge yet? Keep us posted. Only three that I know of, but there could be others. Maybe they'll come out of the woodwork when the bugs show up :-) Sterling .