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

Maximum call stack size exceeded #220

Closed
adminy opened this issue Jul 10, 2018 · 5 comments
Closed

Maximum call stack size exceeded #220

adminy opened this issue Jul 10, 2018 · 5 comments
Labels

Comments

@adminy
Copy link

adminy commented Jul 10, 2018

.....
cpu.js:479 RangeError: Maximum call stack size exceeded
at vd (cpu.js:3684)
at ud.L.rf (pic.js:157)
at lb (cpu.js:3698)
at Xe (cpu.js:2074)
at vd (cpu.js:3680)
at ud.L.rf (pic.js:157)
at lb (cpu.js:3698)
at Xe (cpu.js:2074)
at vd (cpu.js:3680)
at ud.L.rf (pic.js:157)
cpu.js:478 RangeError: Maximum call stack size exceeded
at vd (cpu.js:3684)
at ud.L.rf (pic.js:157)
at lb (cpu.js:3698)
at Xe (cpu.js:2074)
at vd (cpu.js:3680)
at ud.L.rf (pic.js:157)
at lb (cpu.js:3698)
at Xe (cpu.js:2074)
at vd (cpu.js:3680)
at ud.L.rf (pic.js:157)
cpu.js:479 RangeError: Maximum call stack size exceeded
at vd (cpu.js:3684)
at ud.L.rf (pic.js:157)
at lb (cpu.js:3698)
at Xe (cpu.js:2074)
at vd (cpu.js:3680)
at ud.L.rf (pic.js:157)
at lb (cpu.js:3698)
at Xe (cpu.js:2074)
at vd (cpu.js:3680)
at ud.L.rf (pic.js:157)
cpu.js:482 Uncaught RangeError: Maximum call stack size exceeded
at vd (cpu.js:3684)
at ud.L.rf (pic.js:157)
at lb (cpu.js:3698)
at Xe (cpu.js:2074)
at vd (cpu.js:3680)
at ud.L.rf (pic.js:157)
at lb (cpu.js:3698)
at Xe (cpu.js:2074)
at vd (cpu.js:3680)
at ud.L.rf (pic.js:157)

Works fine with qemu, Freezes in browser and this is the error I get.

@niaow
Copy link

niaow commented Jul 10, 2018

I believe that the programmable interrupt conttoller is triggering infinite recursion of interrupts by calling a new interrupt during acknowledgement here: https://github.com/copy/v86/blob/master/src/pic.js#L157

@copy
Copy link
Owner

copy commented Jul 10, 2018

@adminy Could you attach or link us to the disk image and provide reproduction steps?

@adminy
Copy link
Author

adminy commented Jul 10, 2018

@copy I've uploaded the image here: https://drive.google.com/file/d/1fKKgWaQQGzI6BpUY9YtRo4J1nTkUfHj7/view?usp=sharing

I don't know what I did exactly but I got the image running under different build instructions as an iso image rather than img image, I wouldn't know what's causing this but I would like to know.

@adminy
Copy link
Author

adminy commented Jul 13, 2018

A very strange development on this issue happened. I commented out async: true and it got past this error. Pretty Strange I'd say.

But Eventually this error comes up after some time. At least I can use my Os for a little bit before that freezes up.

@copy
Copy link
Owner

copy commented Jul 13, 2018

Interesting find, I'm looking into it.

@copy copy added the bug label Jul 13, 2018
@copy copy closed this as completed in 0fdd143 Jul 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants