Opened 9 years ago

Closed 6 years ago

#7243 closed bug (invalid)

WebPositive crash-error on startup

Reported by: deejam Owned by: leavengood
Priority: normal Milestone: R1
Component: Applications/WebPositive Version: R1/alpha2
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

I get a crash error message every time I start WebPositive. If I ignore the error and continue using WebPositive, it seems to work just fine.

Haiku hrev40501 GCC2. WebPositive hrev573.

Attachments (3)

WebPositive-error-bt (5.3 KB ) - added by deejam 9 years ago.
webpositive_startup_error.png (9.9 KB ) - added by deejam 9 years ago.
WebpageIcons.db (239.0 KB ) - added by deejam 9 years ago.
db-file that causes the crash error

Download all attachments as: .zip

Change History (8)

by deejam, 9 years ago

Attachment: WebPositive-error-bt added

by deejam, 9 years ago

in reply to:  description comment:1 by deejam, 9 years ago

Replying to deejam:

Haiku hrev40501 GCC2. WebPositive hrev573.

It is GCC2 Hybrid. My bad.

comment:2 by deejam, 9 years ago

Deleting /boot/home/config/settings/WebPositive/WebpageIcons.db solves the issue.

Last edited 9 years ago by deejam (previous) (diff)

by deejam, 9 years ago

Attachment: WebpageIcons.db added

db-file that causes the crash error

comment:3 by luroh, 9 years ago

I can repeat the problem with the attached file.

~> sqlite3 /boot/home/config/settings/WebPositive/WebpageIcons.db .tables
Error: database disk image is malformed

comment:4 by mmadia, 7 years ago

Hi. Our WebKit port (and thus WebPositive) was updated in July. Could you retest this in a new nightly image and report back? http://www.haiku-files.org/haiku/development Thanks!

comment:5 by pulkomandy, 6 years ago

Resolution: invalid
Status: newclosed

I guess your icon database got corrupted. Since this never happened again (or to anyone else), I'm going to close this as invalid and assume it was a disk or FS glitch.

We can't really avoid the crash on our side as it happens deep inside WebKit. Maybe they already got it fixed, anyway.

Note: See TracTickets for help on using tickets.