Thanks a lot Zoltan. It has worked and saved my life :) On Sat, Oct 20, 2012 at 12:10 AM, Zoltan Horvath <zol...@webkit.org> wrote:
> Hi Dipak, > > You should try a clean build with build-webkit --system-malloc to force > WebKit to use the system's allocator. > > Let me know if it solves your problem. > > Cheers, > <Zoltan> > > On Fri, Oct 19, 2012 at 5:21 AM, dipak kumar <mail.di...@gmail.com> wrote: > >> Dear All, >> >> I have built Webkit (Process model) for Win32. I have developed a client >> application to use this webkit. >> My client application has a number of new/delete calls. Now when I run >> the client application it crashes >> at the location where memory is being freed. Call stack shows the crash >> point at free of JavaScriptCore. >> This free is inside fastmalloc.cpp. >> >> >> #if >> >> ENABLE(WTF_MALLOC_VALIDATION) >> >> if (!ptr) >> >> return; >> >> fastMallocValidate(ptr); >> >> Internal::ValidationHeader* header = >> Internal::fastMallocValidationHeader(ptr); >> >> memset(ptr, 0xCC, header->m_size); >> >> do_free(header); >> >> #else >> >> *do_free(ptr); >> ----------------->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> CRASH POINT* >> >> #endif >> >> >> >> Please let me know how can I stop my client application to get linked to >> JavaScriptCore memory functions. >> >> >> >> Awaiting reply. >> >> >> >> Many Thanks, >> >> Dipak >> >> >> >> _______________________________________________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> http://lists.webkit.org/mailman/listinfo/webkit-dev >> >> >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
