Beta 5 Crash when trying to select collection for Cited By tool

I have a study layout open with the cited by tool as part of the saved layout. When I click on the cited by tab and then go to the menu to select the collections it searches I can remove selections that are already checked, but if I try to check a collection to be searched by the tool I get a crash. Crash log attached.

8475.Logos4Crash.txt

Find more posts tagged with

Comments

Dave Hooton

confirmed....

0508.Logos4Crash.txt

JimTowler

https://community.logos.com/discussion/comment/120738#Comment_120738

I'm just thinking ...

Logos4 often crashes and dumps a log of the stack trace. Thats OK, and its a Beta, and the bug needs to get fixed. All Good.

HOWEVER, what if the application did more TRY ... CATCH stuff, and kept the error in=house, dumpped the log, prompted the user to auto-submit the fault report (YES/NO?), then continued to operate anyway ... ???

1) Us users would not actually crash out of the application. (But of course the attempted function still fails, but it does at present).
2) The Application would keep control of the stack trace data, current context, attempted function etc, and have control of what happens next.
3) The Dev Team gets a formatted log of whatever the application can trace, as long as the user selectes to submit the report, or has enabled the auto-submit setting. (Internally, various portions of the program can create bread-crumb trails of selected data, at least in the Betas, and have a great context automattically.)

Please?

Fred Chapman

https://community.logos.com/discussion/comment/120743#Comment_120743

I'm just thinking ...

Logos4 often crashes and dumps a log of the stack trace. Thats OK, and its a Beta, and the bug needs to get fixed. All Good.

HOWEVER, what if the application did more TRY ... CATCH stuff, and kept the error in=house, dumpped the log, prompted the user to auto-submit the fault report (YES/NO?), then continued to operate anyway ... ???

1) Us users would not actually crash out of the application. (But of course the attempted function still fails, but it does at present).
2) The Application would keep control of the stack trace data, current context, attempted function etc, and have control of what happens next.
3) The Dev Team gets a formatted log of whatever the application can trace, as long as the user selectes to submit the report, or has enabled the auto-submit setting. (Internally, various portions of the program can create bread-crumb trails of selected data, at least in the Betas, and have a great context automattically.)

Please?

I'm a preacher not a programmer and know just enough about hardware and software to be dangerous; so I don't really know what all that means Jim.[*-)]

JimTowler

https://community.logos.com/discussion/comment/120797#Comment_120797

I'm a preacher not a programmer ... so I don't really know what all that means

Oh just me mouthing off a little about why the program can't just take care of it, log something, and not actually crash!

(On a future day, once this is implemented, I'll ask for the ability to disable an automatic send of the log report. [:S])

Aaron Sauer

hey, me too

5488.Logos4Crash.txt

MJ. Smith

https://community.logos.com/discussion/comment/120807#Comment_120807

why the program can't just take care of it, log something, and not actually crash!

I'll admit that I am always amazed at how willing programmers of PC apps are willing to let a machine crash. There are many apps where crashes simply cannot be allowed to occur so I know it isn't asking the impossible.

Melissa Snyder

Crash report is submitted to development. Thanks.

Update: This will be fixed in the next beta.