This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Hello, in certain circumstances (sic) Amaya crashes when double clic on a link with this report: Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0000028c Thread 0 Crashed: 0 fr.inria.amaya 0x0031ecc8 wxMacTopLevelMouseEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1520 1 fr.inria.amaya 0x0031f90c wxMacTopLevelEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 196 2 com.apple.HIToolbox 0x932af934 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692 3 com.apple.HIToolbox 0x932af08c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372 4 com.apple.HIToolbox 0x932b5e90 SendEventToEventTarget + 40 5 com.apple.HIToolbox 0x93342230 HandleMouseEventForWindow(OpaqueWindowPtr*, OpaqueEventRef*, unsigned short) + 236 6 com.apple.HIToolbox 0x934a53e8 HandleMouseEvent(OpaqueEventRef*) + 368 7 com.apple.HIToolbox 0x932b61fc ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 496 8 com.apple.HIToolbox 0x932afb84 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1284 9 com.apple.HIToolbox 0x932af08c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372 10 com.apple.HIToolbox 0x932b5e90 SendEventToEventTarget + 40 11 fr.inria.amaya 0x0037aaf8 wxApp::MacHandleOneEvent(void*) + 44 12 fr.inria.amaya 0x0037aa10 wxApp::MacDoOneEvent() + 164 13 fr.inria.amaya 0x004cefe4 wxEventLoop::Dispatch() + 52 14 fr.inria.amaya 0x004ca3e0 wxEventLoopManual::Run() + 252 15 fr.inria.amaya 0x00389298 wxAppBase::MainLoop() + 128 16 fr.inria.amaya 0x00374e20 wxEntry(int&, wchar_t**) + 124 17 fr.inria.amaya 0x00143088 main + 24 18 fr.inria.amaya 0x000022a0 _start + 392 (crt.c:267) 19 dyld Exception: EXC_BAD_ACCESS (0x0001) Hope this help, Pascal.
Unfortunately we're not able to reproduce that bug and the trace doesn't help. If you find out a scenario able to reproduce it, please reopen the bug.