Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

intermittent segfault messages #3

Open
bebbi opened this issue Dec 3, 2014 · 3 comments
Open

intermittent segfault messages #3

bebbi opened this issue Dec 3, 2014 · 3 comments

Comments

@bebbi
Copy link
Contributor

bebbi commented Dec 3, 2014

Like this:
segmentation fault loading 1 bytes from address 0
index.html:54 segmentation fault loading 1 bytes from address 0
VM148:1 segmentation fault loading 1 bytes from address 0

No way to reproduce, happens more or less depending on number of clouds in the sky. I had it on different occasions, when opening or reloading the page, or otherwise - once I even had it occur during a debugging session where I stepped through code that only did jQuery dicomDOM processing. With one arbitrary step, the error was there.

@pieper
Copy link
Member

pieper commented Dec 8, 2014

Weird. I have never seen this.

To clarify: is this a message that shows up in the console, or does chrome
as a whole crash?

On Wed, Dec 3, 2014 at 4:12 PM, Stefan notifications@github.com wrote:

Like this:
segmentation fault loading 1 bytes from address 0
index.html:54 segmentation fault loading 1 bytes from address 0
VM148:1 segmentation fault loading 1 bytes from address 0

No way to reproduce, happens more or less depending on number of clouds in
the sky. I had it on different occasions, when opening or reloading the
page, or otherwise - once I even had it occur during a debugging session
where I stepped through code that only did jQuery dicomDOM processing. With
one arbitrary step, the error was there.


Reply to this email directly or view it on GitHub
#3.

The information in this e-mail is intended only for the person to whom it
is
addressed. If you believe this e-mail was sent to you in error and the
e-mail
contains patient information, please contact the Partners Compliance
HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in
error
but does not contain patient information, please contact the sender and
properly
dispose of the e-mail.

@bebbi
Copy link
Contributor Author

bebbi commented Dec 8, 2014

I haven't seen it in a while. A resource problem? Seems to come from dcmtk.js area. I haven't looked at files produced when seeing this, but was behaving completely noninvasive, ie no crash or even an error on js side. Got logged to console AND the status dom, so it appears it was nicely using the print (or status?) command

On 08.12.2014, at 20:51, Steve Pieper notifications@github.com wrote:

Weird. I have never seen this.

To clarify: is this a message that shows up in the console, or does chrome
as a whole crash?

On Wed, Dec 3, 2014 at 4:12 PM, Stefan notifications@github.com wrote:

Like this:
segmentation fault loading 1 bytes from address 0
index.html:54 segmentation fault loading 1 bytes from address 0
VM148:1 segmentation fault loading 1 bytes from address 0

No way to reproduce, happens more or less depending on number of clouds in
the sky. I had it on different occasions, when opening or reloading the
page, or otherwise - once I even had it occur during a debugging session
where I stepped through code that only did jQuery dicomDOM processing. With
one arbitrary step, the error was there.


Reply to this email directly or view it on GitHub
#3.

The information in this e-mail is intended only for the person to whom it
is
addressed. If you believe this e-mail was sent to you in error and the
e-mail
contains patient information, please contact the Partners Compliance
HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in
error
but does not contain patient information, please contact the sender and
properly
dispose of the e-mail.


Reply to this email directly or view it on GitHub.

@pieper
Copy link
Member

pieper commented Dec 8, 2014

Okay, yes, makes sense. We'll just keep an eye our for it for now.

On Mon, Dec 8, 2014 at 3:06 PM, Stefan notifications@github.com wrote:

I haven't seen it in a while. A resource problem? Seems to come from
dcmtk.js area. I haven't looked at files produced when seeing this, but was
behaving completely noninvasive, ie no crash or even an error on js side.
Got logged to console AND the status dom, so it appears it was nicely using
the print (or status?) command

On 08.12.2014, at 20:51, Steve Pieper notifications@github.com wrote:

Weird. I have never seen this.

To clarify: is this a message that shows up in the console, or does
chrome
as a whole crash?

On Wed, Dec 3, 2014 at 4:12 PM, Stefan notifications@github.com
wrote:

Like this:
segmentation fault loading 1 bytes from address 0
index.html:54 segmentation fault loading 1 bytes from address 0
VM148:1 segmentation fault loading 1 bytes from address 0

No way to reproduce, happens more or less depending on number of
clouds in
the sky. I had it on different occasions, when opening or reloading
the
page, or otherwise - once I even had it occur during a debugging
session
where I stepped through code that only did jQuery dicomDOM processing.
With
one arbitrary step, the error was there.


Reply to this email directly or view it on GitHub
#3.

The information in this e-mail is intended only for the person to whom
it
is
addressed. If you believe this e-mail was sent to you in error and the
e-mail
contains patient information, please contact the Partners Compliance
HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to
you in
error
but does not contain patient information, please contact the sender
and
properly
dispose of the e-mail.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub
#3 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants