Opened 13 years ago
Closed 10 years ago
#8027 closed bug (invalid)
Web+ crashed on context menu
Reported by: | humdinger | Owned by: | leavengood |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/WebPositive | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
This is hrev42858 coming with web+ hrev583.
Web+ crashed on me after opening a link in another tab by right-clicking a link. The new tab did appear, so the crash must have happened after clicking the context menu item.
Backtrace:
[tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 285 caused an exception: Segment violation [...] [Switching to team /boot/apps/WebPositive/WebPositive https://www.haiku-os.org/s/d (285) thread WebPositive (285)] 0x00a1deeb in WebCore::ContextMenuController::contextMenuItemSelected () from /boot/apps/WebPositive/lib/libwebcore.so (gdb) bt #0 0x00a1deeb in WebCore::ContextMenuController::contextMenuItemSelected () from /boot/apps/WebPositive/lib/libwebcore.so #1 0x00acbbf4 in WebCore::ContextMenu::ContextMenuHandler::MessageReceived () from /boot/apps/WebPositive/lib/libwebcore.so #2 0x00000000 in ?? () #3 0x7ffeec3c in ?? () #4 0x7ffeec48 in ?? () #5 0x00acbb7e in WebCore::ContextMenu::ContextMenuHandler::MessageReceived () from /boot/apps/WebPositive/lib/libwebcore.so Previous frame inner to this frame (corrupt stack?) (gdb)
Syslog:
KERN: vm_soft_fault: va 0x0 not covered by area in address space KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x8, ip 0xa1deeb, write 0, user 1, thread 0x11d KERN: vm_page_fault: thread "WebPositive" (285) in team "WebPositive" (285) tried to read address 0x8, ip 0xa1deeb ("libwebcore.so_seg0ro" +0x5c9eeb) KERN: debug_server: Thread 285 entered the debugger: Segment violation KERN: stack trace, current PC 0xa1deeb _ZN7WebCore21ContextMenuController23contextMenuItemSelectedEPNS_15ContextMenuItemE + 0x4b: KERN: (0x7ffeec18) 0xacbbf4 _ZN7WebCore11ContextMenu18ContextMenuHandler15MessageReceivedEP8BMessage + 0x84 KERN: (0x7ffeec58) 0x2c0edb4 _ZN7BLooper15DispatchMessageEP8BMessageP8BHandler + 0x34 KERN: (0x7ffeec78) 0x2c0797f _ZN12BApplication15DispatchMessageEP8BMessageP8BHandler + 0x2f KERN: (0x7ffeeeb8) 0x2c1029b _ZN7BLooper11task_looperEv + 0x25b KERN: (0x7ffeef08) 0x2c05ca3 _ZN12BApplication3RunEv + 0x53 KERN: (0x7ffeef28) 0x23ad13 main + 0x43 KERN: (0x7ffeef68) 0x22885d _start + 0x51 KERN: (0x7ffeef9c) 0x10621a runtime_loader + 0x14e
Change History (2)
comment:1 by , 11 years ago
comment:2 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
No response. Closing as invalid.
Note:
See TracTickets
for help on using tickets.
Can anyone reproduce this?