#19199 closed bug (invalid)
Dooble very unstable on Haiku
| Reported by: | Vannura | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | - General | Version: | R1/beta5 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
The issue is very random, sometimes is when i open or close the tab, other times is at nowhere (just doing nothing) and even when i just open it. On a worse case it even crash Haiku.
Attachments (14)
Change History (21)
by , 4 weeks ago
| Attachment: | Debugger-19388-debug-24-10-2024-02-21-30.report added |
|---|
by , 4 weeks ago
| Attachment: | Dooble-451-debug-22-10-2024-20-03-30.report added |
|---|
by , 4 weeks ago
| Attachment: | Dooble-534-debug-24-10-2024-02-21-09.report added |
|---|
by , 4 weeks ago
| Attachment: | Dooble-534-debug-24-10-2024-02-21-34.report added |
|---|
by , 4 weeks ago
| Attachment: | Dooble-9076-debug-22-10-2024-18-41-22.report added |
|---|
by , 4 weeks ago
| Attachment: | Dooble-10583-debug-24-10-2024-00-18-43.report added |
|---|
by , 4 weeks ago
| Attachment: | Dooble-10583-debug-24-10-2024-00-18-43.2.report added |
|---|
by , 4 weeks ago
| Attachment: | QtWebEngineProcess-980-debug-24-10-2024-16-37-20.report added |
|---|
by , 4 weeks ago
| Attachment: | QtWebEngineProcess-18601-debug-24-10-2024-21-40-35.report added |
|---|
by , 4 weeks ago
| Attachment: | QtWebEngineProcess-21143-debug-24-10-2024-21-43-04.report added |
|---|
by , 4 weeks ago
| Attachment: | QtWebEngineProcess-44618-debug-23-10-2024-22-16-29.report added |
|---|
by , 4 weeks ago
| Attachment: | QtWebEngineProcess-45436-debug-23-10-2024-22-17-03.report added |
|---|
by , 4 weeks ago
| Attachment: | QtWebEngineProcess-63140-debug-23-10-2024-23-34-40.report added |
|---|
by , 4 weeks ago
| Attachment: | QtWebEngineProcess-980-debug-24-10-2024-16-37-20.2.report added |
|---|
follow-up: 2 comment:1 by , 4 weeks ago
comment:2 by , 4 weeks ago
Replying to waddlesplash:
This is not the place to report bugs in ported applications. If you have Haiku crashes, you can post them here, but most of these just look like problems with the port.
jt15s said to do that here...
comment:3 by , 4 weeks ago
Well, that's incorrect.
If you have screenshots of crashes in Haiku itself caused by Dooble, then do attach those here. Otherwise this ticket will just be closed.
comment:4 by , 4 weeks ago
My apologies, Vannura was posting all of these logs on the Haiku Discord server so I directed them here. I wasn't aware that Dooble wasn't a native application. I'll find the right place to report bugs for Dooble and direct Vannura there.
Again, apologies for any inconvenience caused.
comment:5 by , 4 weeks ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:6 by , 4 weeks ago
jt15s: It's not about native vs non-native but rather in-tree vs out of tree.
If it is a native app the the issues should be reported to that specific developer, if ported then to the porter first (unless this is an official upstream port and upstream wants to support it)
Also note that whatever discord guild that is isn't official ;)
comment:7 by , 4 weeks ago
Thanks, I'll keep that in mind for next time.
Also, yes, I'm aware that the Discord server isn't official, but it is recognised by Haiku as an unofficial community group and it is listed on the Haiku website. I'm a moderator on there, and we do make it very clear that we're a community group but not an official platform. We often have users posting about issues/bugs that they encounter with Haiku in the hope that someone on Discord can help them out (but it's either a case of the devs not being on Discord or rarely checking), so I always make sure to direct people to Trac where possible so the issue can be triaged/resolved (people don't seem to know that they should file a bug report on Trac if they run into issues so this may be a case of needing clearer communication around this within Haiku itself).
This is not the place to report bugs in ported applications. If you have Haiku crashes, you can post them here, but most of these just look like problems with the port.